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?
Taming HTML5 and JS: High Performance Mobile, WebKit, FireFox Dev Tools @QCon New York
Agile Development: A Manager's Roadmap for Success
Architectures You've Always Wondered About @QCon New York
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!
I thought that was a really great talk and really pleased I spent the hour watching it.
I have a question regarding transactions. In the system it shows trades entering the distributed cache via messaging e.g. point to point queue or topic which it subscribes to. It also says that persistence is via Hibernate mappings which are invoked asynchronously. I just wanted to get a feel for how the transactions work in this system e.g. in terms of trades entering the system does an initial persistence action take place, which has to succeed before the transactions with the queue or topic ends (so you don't lose the trade). When events are being executed against the domain objects and the data is changing, it's implied that async calls keep the persistence state synced with the cache state. How does the system ensure that writes aren't lost e.g. if the persistence is asynchronous how would you rollback the cache data if that action fails.
Thanks again.
Yes, I didn't expand on this area in the presentation. But within the transaction that takes the trade message off the topic, as well as the trade being saved to the cache it is also written to a file. The trades from the file are then persisted to the database via Hibernate asynchronously. Therefore the database call is out of the critical path, but the trade is persisted, initially to just a file.
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.
2 comments
Watch Thread Reply