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.
How would you like to view the presentation?
Could you post them again?
Hi Eric,
Thanks a lot for letting us know. The problem has been fixed.
I think this one of the first SOA presentations I have seen, where the presenter really understands what SOA is.
Great!
Tor,
I am not quite sure where you see any particular knowledge about SOA in this presentation. Somebody who does not understand (let alone speak about) the relationship between reuse and service versioning has no understanding whatsoever about SOA. Somebody who does not understand that one of the key principle of SOA is the decoupling of the interface from the implementation (something that REST 99% of the REST developer don't practice) and claim that an ESB has no value, has never found SOA. You don't have to spend millions to achieve this separation, but not understanding how core it is, is very sad.
The author may think that he speaks about SOA but he doesn't. He may have achieved building some "usable" software apply EVO principles, but by a large margin he has never build a "service". The author points rightfully that "reuse" couples service consumers, but he has no understanding on how to use SOA technologies to minimize this coupling and therefore rip the benefits behind SOA. This is why the author claims that "reuse" is "overrated".
For the record, "reuse" doesn't have to be designed. It can't be designed. In SOA, reuse happens the other way around, it is not new consumers who reuse existing services, it is the old consumers who reuse new service versions (without any change) as the service evolve to meet the needs of new consumers. Anybody who is trying to design a service that can be reused 3 years from today is wasting everybody's time and resources. Governance does not yield reuse.
It is sad that in 2011, people still propagate this kind of deeply to and totally flawed message about SOA.
JJ-
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.
4 comments
Watch Thread Reply