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 Geoffrey Wiseman on Aug 22, 2007
Now that Agile2007 is over many people have looked back over the conference and shared their experiences.
Computer Business Review pointed out that Agile methods have come full circle, where software development took some of its inspiration for agile methods from manufacturing, and now manufacturing companies are adopting methods from software development, and draws parallels between manufacturing and software development:
Like IT, for many years, manufacturing was a protected industry and profession until offshore competition applied practices developed in the western world to produce faster, better, cheaper.
Fast forward 20 years, change the sector to IT, and the offshore colossus to India, and the parallels are incredibly similar.
Tony Bauer's roundup (via ComputerWire) talked about scaling Agile to the Enterprise:
Although there was no official theme to this year's Agile development conference, clearly much of the message concerned how to scale agile to the point where it could be taken seriously by the enterprise.
Whereas the typical team might have topped out at 15 members a year ago, Barton [CTO for SolutionsIQ] is increasingly seeing agile project teams numbering as many as 25 members.
Ultimately, though, Bauer argued that Agile methods aren't quite ready for full-scale enterprise adoption:
Yet the proposals and ideas delivered at Agile 2007 demonstrate that while agile is starting to scale, it still has along way to go before the methodology becomes robust enough for enterprise deployment.
The Sherpa Project reviewed some favorite sessions, and walked through some realizations and concerns in Agile 2007 - Parting Thoughts:
- Lean thinking has started to move to the center of the agile universe.
- Everyone wants to scale agile.
- Everyone wants to distribute agile.
- Lean has moved to buzzword status. A lot of people are talking about Lean but I don't think the majority understand the essence behind it. I think this will get better.
- Everyone wants to make "Enterprisey" software with agile teams.
- There are a lot of "agile" consulting firms that are full of ...
I think the fact that everyone is focused on "scaling" agility to large teams and distributed projects and that there will be a lot of agile disasters over the next couple of years. Now that the bigger software companies are moving to agile, the teams are getting too big and they are adopting agile in scary ways (too big, too fast). I think that you need to evolve to big teams, not start out there. I would also (passionately) argue that you should focus on how to have smaller software instead of how to scale agile teams to accommodate large software. I seem to be in the minority.
Were you at Agile 2007? How was the experience for you?
Agile Maturity Model Applied to Building and Releasing Software
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
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.
1 comment
Watch Thread Reply