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?
Great presentation and quite relevant to SOA and BPM architects. In fact, RESTful services are demonstrably compliant with SOA design principles. Of course, when implementing REST-style services, architects still see the same governance, management and other QoS (security, SLA's) requirements as with SOAP-style services.
Is there any chance to get the source of the example??
Thank you
Marina, not sure about the modified source Cesare presents, but the actual RESTBucks code is available from the REST In Practice book page.
Great presentation, we need more time to discuss many approaches here. Unfortunately we need to have some time explaining both concepts.
OK, it is not that clear from presentation what is the integration approach, or how can I use REST in the BPM world. It is mentioned, I guess it is not stressed enough.
When you talk about BPM and then you talk about Services, common understanding is using a modeling language (BPEL) to invoke services in a workflow. That flow is called a Business Process (BP). If we mention REST Web Services, the immediate assumption is we will use BPEL to invoke a REST WS.
That idea is reinforced in the talk when Cesare presents the connectors slide, comparing RCP, Messaging and REST "connectors". The idea of expanding BPEL to be able to invoke REST WS is mentioned somewhere too.
But later on, the other idea is presented succinctly. The resource concept is to broad, we can use it to represent the whole BP itself. Actually, the BP modeling can happen directly using the Hypermedia and state combination REST is famous about. And that approach is the one presented in the last part of the talk. In other words, I can actually model a BP using REST!.
Anyhow, both approaches have some mismatches if we think of BPs as a flow of services invocations. For instance, REST as a BP workflow engine implies one BP task is actually an interaction with a resource, very different from a service invocation. One of my claims is that we can use services and SOA to implemented BPs, but they are not the only way, thus the REST approach is perfectly valid, although not the one we are used to.
The idea is a good one, needs to be further discussed though.
Cheers.
William Martinez Pomares.
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