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 Richard Seroter on May 24, 2011
In a recent report, Gartner revealed that only 9% of Enterprise Architecture (EA) endeavors are done in partnership with the business side of an organization. While the percentage of collaborative projects is expected to increase to 30% by 2016, to some this is still an alarmingly low level of involvement by EA teams who run the risk of being bypassed when business groups make technical decisions.
Many saw Gartner’s results as indicative of EA’s failures to serve its primary purpose which is to describe the architecture of the enterprise in order to increase the effectiveness of the business. Joe McKendrick is concerned that even if 30% of projects in 2016 are collaborations between the business and IT, this still means that the majority of EA efforts are IT-centric. eBizQ is hosting a discussion on this topic and the responses consistently decry the confusion about the role of EA and the missed opportunities for both EA and business counterparts to work together to realize business objectives in a way that will optimize the existing enterprise IT strategy. If EA departments cannot fulfill the role of trusted advisor to the business, they run the risk of being marginalized resulting in stalled IT optimization efforts.
However, the picture is not entirely bleak. Multiple factors have contributed to the acceleration towards a more business-integrated EA team. Gartner cites the business’s increased capability to make independent technology decisions, management pressure on EA teams to deliver tangible business value, and the growing CIO opinion that IT strategies should align with business priorities.
Alex Cullen of InfoWorld points out a recent Forrester study that highlights the increased support for EA programs when they have an active business architecture discipline. This trend is reinforced by early submissions to the Forrester/InfoWorld 2011 Enterprise Architecture Awards. Cullen says:
I've talked with pharmaceutical firms that report crafting a much more blended business/IT operating model, a telecom firm whose EAs help business understand the scope of business transformation programs, and a manufacturer where the EA team is helping the business to understand how to utilize existing capabilities when venturing into new business areas or geographies.
The movement towards a more business-integrated IT department is was also clearly evident in last year’s Enterprise Architecture awards. The winning companies shared a number of characteristics that led to their success. Enterprise Architects at both Barclay’s Bank and Discover Financial Services have significant input into project portfolio management and can help prioritize projects and ensure compliance with a greater architectural vision. According to Barclay’s, EA teams that can effectively collaborate with diverse business stakeholders such as finance, planning and operations have a greater chance of success. Each of the winning EA groups appeared to have strong mandates to pursue their endeavors but it seems clear that if they had stumbled in their efforts, they would not have retained their influential position.
The EA discipline will likely look much different in 2016 than it does today as more EA programs move away from IT-only initiatives and become more entrenched in the business domain.
Systems Engineering for Dummies eBook
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Adopting Git for the Enterprise: Risks and Considerations
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!
This is a great recap Richard. I wrote up a complementary post to this one. See the link below:
www.mikethearchitect.com/2011/05/by-2016-30-per...
Best Regards,
Mike Walker
www.mikethearchitect.com
Looks like the link is broken
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