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 Peter Cooper on Oct 02, 2006
In a speech at the 2006 MIT Emerging Technologies Conference, Jeff Bezos, founder of Amazon.com, has pointed out that 70% of the time spent on a project is spent on inconsequential tasks that don't differentiate that project from any other. Bezos calls these features "muck" and suggests developers could outsource their implementation to third parties or technologies, much in the same way business owners outsource generic tasks like accounting, finance, and legal services.
In an overview for Artima Developer, Frank Sommers looks at Bezo's observations and suggests that Rails is an ideal tool for reducing the level of "muck" in a project, along with technologies such as Amazon's S3 storage API. With Jeff Bezos' recent investment in Rails-founders 37signals, a company that strongly believes in focusing on differentiation from competitors (mostly by providing a simple, user-friendly service) it seems Bezos is putting his money where his mouth is.
Agile Development: A Manager's Roadmap for Success
The WebSphere Liberty Profile for Developers: An Introduction
RDBMS to NoSQL: Managing the Transition
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Sure, he mentioned Rails, but there's plenty of pre-built infrastructure out there for Java... More than Ruby, in fact, especially if you want to build enterprise systems that do real work...
Except that Amazon already uses plenty of Java inside. Bezos knows that, knows what Java is good (and not so good) for, and he's still suggesing that RoR is a good solution for the 70% of the 'muck'.
Looking back, it wasn't Bezos who suggested RoR was a good fit, it was Frank Sommers from Artima. Bezos was probably positioning the web services Amazon provides (like S3) as that outsourced infrastructure.
I still say in terms of real enterprise infrastructure, Java is in a much better position to provide the muck.
Some other guy did.
Yea, outsource your crap to somebody else to do. This is really big news to people?
Frankly - i'm getting sick and tired of hearing about how Ruby should be used for everything short of making coffee in the morning (and some people argue it would do a better job for that!).
Look at where you are today, look at where you want to go tomorrow and the day after, and pick the best tool to get yourself there. Period.
.. really lame. Desperate stuff like this is what gives a nice technology a bad name.
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.
5 comments
Watch Thread Reply