Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Scott Delap on Aug 29, 2008
Let’s face it: The client has not been a friendly place for Java programmers. Java technology on the client with applets, Swing, and JavaFX has had limited success. JavaScript, despite its name, is almost nothing like the Java language. And Adobe Flash—well, it’s just like JavaScript. Or is it? It might have been the case that Flash was like JavaScript a couple of years ago, but with the advent of ActionScript 3, a lot has changed. And I think you’ll find a lot to like.First, ActionScript—the programming language for Adobe Flex and Flash—is now strongly typed. It also has first-class object orientation, including classes and interfaces. It has extras that you won’t find in Java—notably, get and set functions for properties and a language extension called ECMAScript for XML (E4X), which turns any XML document into objects that you can reference with dot operators, just like regular objects.
This article takes you through the basics of ActionScript 3 and shows how it compares with the Java environment you’re used to. By the end, you should have given up any preconceptions you may have had about ActionScript...
Continue Reading ActionScript 3 for Java Programmers
Introducing SQLFire: a memory-optimized, high performance SQL database
The WebSphere Liberty Profile for Developers: An Introduction
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
Tools to unit test your JavaScript
Combining Inspections, Static Analysis, Testing to Achieve >95% Defect Removal Efficiency
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
Often the hardest part of changing technologies is language syntax differences
That is not true. Often, language syntax is the LEAST and EASIEST part, when changing technologies. As an example. Going from Java development into RIA development with Flex and AS3, the hardest part is learning the new platform. Best ways to do things. Learning the flex apis. Idioms and best-practices.
Learning the syntax of AS3 is a no-brainer for a just a little bit experienced developer.
I agree. The syntax is the easiest part. The hardest is that often, the best practice in language A, -can- be used in Language B, but its awful, horribly inefficient, etc, and you end up not knowing any better at first. Learning the set of best practices and idioms is where the challenge is. Because of that, most people don't even try, and it ends up in a huge mess :)
This is a common case for me. I have learned to hire Java Developers and teach them flash (Flex AS3). As others have said, its not the Syntax, its the idea of interactive Objects within a Time Line, that's a bit harder to deal with. The Flash program is a bit of a pain as the UI is not developer friendly, but using Eclipse / Flex is much easier for a developer to pick up.
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
3 comments
Watch Thread Reply