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 Michael Stal on Aug 05, 2011
The International Software Product Line Conference (SPLC) is the most important event that covers the full range of Product Line Engineering in software-intensive products. Its 15th incarnation will take place in the Munich City Center from August 21st to August 26th.
According to the CMU SEI (Carnegie-Mellon University Software Engineering Institute ) a software product line is defined as
a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
Software product lines are important as they enable systematic reuse instead of ad-hoc reuse on a large scale. For this purpose, the product line platform provides a set of core assets such as components, test plans, documents that are relevant for all products supposed to be in the scope of the product line. Building software product lines and in particular their architectures, however, is very challenging because they must be able to cope with all commonalities and variability across the targeted products. This is the reason why there is still so much research and industrial practice necessary to raise the maturity of the field.
The SPLC conference attempts to receive interesting contributions from both industry and research every year. The program committee as well as the list of speakers comprise some of the best known experts in software architecture. Hence, the event also provides a great opportunity for networking.
The upcoming SPLC in Munich will offer many interesting topics. Off course, there will be a large program full of submitted papers. And there will be a whole bunch of tutorials. For example, ones about development, operation, or requirements management for as well as tutorials covering tools, industry trends, DSLs, and real-world experiences.
Keynotes will be given by
Last but not least there’ll be two panels, one on “Standards for Variability Modeling” and another one on “The End of the Line” dealing how to recognize that a product line has reached the end of its lifetime, and how to manage this.
In conclusion, the venue and the program appear very attractive. So if you are interested in the details of the program you may download the preliminary program schedule.
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
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!
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.
No comments
Watch Thread Reply