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 Dave West on Aug 06, 2010
Ryan Martens used his blog to talk about the relationship between collaborative and cooperative work, like that done by Agile teams, and the physical environment in which they work. More specifically, he relates some of the work on designing furnishings and whole spaces being done at the Stanford d.School.
From the very beginning, Agile emphasized the need for a different kind of environment - open space, wall-to-wall whiteboards, big visible charts, and even popcorn machines and refrigerators. This was frequently a hard sell to management committed to cubicles. Martens points out (emphasis is his)
for you and your agile teams, the innovations in team room furniture was really important. Creating a culture of innovation relies on creating the right environment.
and that
As a result of working at the extreme of rapid collaboration, they have come up with some fantastic furniture designs that you should consider copying for your team and meeting rooms. Unfortunately, you can’t buy this stuff – you have to build it locally.
The Stanford d.School is led by David Kelly (long associated with IDEO, and author of several books on design thinking) and some of their results include:
Behind the cool factor are serious issues of how space affects human abilities to communicate and work. Some of these issues have been long recognized in the world of architecture, anthropology, knowledge management and philosophy - but they are just now becoming of significant concern in the business and software development worlds.
Martens mentions the importance of the concept of 'Ba' as a foundation for thinking about Agile work spaces and environments. A discussion of Ba in this context is found at Cyberartsweb.org:
According to the theory of existentialism, Ba is a context, which harbours meaning. Thus, ba can be considered as a shared space that serves as a foundation for knowledge creation. ... According to Nonaka, "Ba" can be thought of as a shared space for emerging relationships. This space can be physical (eg. office, dispersed business space), virtual (e.g., email, teleconference), mental (eg. shared experiences, ideas, ideals) or any combination of them. Ba provides a platform for advancing individual and/or collective knowledge.
Four types of Ba space are recognized: Originating Ba, Interacting Ba, Cyber Ba, and Exercising Ba.
Martens' blog points out that there is value in examining any given agile practice - in this case the design of the agile team work space and furnishings - in order to discover the conceptual foundations behind the practice and to discover how others are exploiting those concepts to introduce innovation.
Continuous Delivery: Anatomy of a Deployment Pipeline
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
How ALM Supports Business Processes
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!
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