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?
Introducing SQLFire: a memory-optimized, high performance SQL database
RDBMS to NoSQL: Managing the Transition
Banking Case Study: Scaling with Low Latency using NewSQL
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
I understand the role OSGi plays in fixing the classpath mess. But I do not understand the need for OSGi’s dynamic service capability for web applications especially when almost all the web applications are shut down to update any small piece of code. If we are shutting down applications for update, what do we gain from OSGi (and its new programming model) other than the fix for classpath? Could someone enlighten me please?
Er, apart from not having to shut down the web application?
I think the benefits includes,
1. Modular
2. Dynamic, for this, it includes several meanings, pluggable service, replace and update service without stopping whole application.
3. Extensible
In some cases it might be relevant not having to shut down the whole system (especially for smaller system which might just run on one node rather than a cluster).
I am imagining a osgi-web-application which has a special bundle that is stopped by default. Once it gets started it will display a message on each page to the user, letting him know that an update of the system will occur soon and that some services might not be available for a short while (updating in OSGi is quick).
When the update occurs the relevant services will be shut down and the consuming bundle has to deal with that, meaning that the user will be presented a message that the service he is trying to acces is curerntly not available. When the service is back everything continues as usual and the update-notifier-bundle can be stopped (until the next release).
This is just a quick idea without putting much time into the details ;)
As Ian states out, having the application handle services going away is cumbersome, and it will be interesting to see how these blueprint-containers will help at this point.
I personally cant wait to try out these WTP plugins...but I should get some rest first :-D
Btw: for me, this is one of the best summaries on OSGi-technology I've found until now. Hope to hear/see more from Ian
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