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?
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agile Maturity Model Applied to Building and Releasing Software
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
Please notice that he draws the circles from the view of ‘selling the product’, so he puts it in that sequence; ’why-how-what’. On the other hand,in my perception, when it comes to the ‘product development’, the sequence is a bit changed to ‘why-what-how’, to reflect the real sequence in development process: (with the same intellectual meaning of each circle)
1- the vision,
2- the needs or requirements, and
3- the specifications
Although it has a bit different perspective (it's about forms of knowledge and leadership), but the following is found so relevant to our 'why-what-how’ conceptualization:
-------------------------------
Aristotle identified three forms of knowledge:
Episteme = universally valid scientific knowledge,
Techne = skill-based technical know-how, and
Phronesis = a true and reasoned state of capacity to act with regard to the things that are good or bad for man.
If episteme is ‘know-why’, and
techne is ‘know-how’,
then phronesis is know-what-should-be-done.
Example: because no universal notion of a good car exists, episteme cannot answer the question “What is a good car?” That will depend on who is using the car and why, and it will change over time. Techne is knowing how to make a car well; phronesis is knowing both what a good car is and how to build it. Thus phronesis enables managers to determine what is good in specific times and situations and to undertake the best actions at those times to serve the common good.
------------------
[The source is: Harvard Business Review (HRB) - The Big Idea: The Wise Leader by Ikujiro Nonaka and Hirotaka Takeuchi]
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