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 Mark Little on May 24, 2007
“SOA is entirely transforming the way IT is created, delivered and consumed, providing organizations with a software and systems infrastructure that is more agile and cost-effective and that delivers better business outcomes. HP is committed to providing the tools and expertise customers need to begin adopting SOA successfully. Our open, standards-based approach maximizes the business benefit from their SOA initiatives.”The suite, called the Business Technology Optimization for SOA (BTO), is apparently an integrated set of software and services designed to help customers address some of the biggest challenges in SOA adoption, including:
“A strong governance, quality and management program – addressing the entire service lifecycle from design and development through operations and maintenance – is critically important to a successful SOA initiative. Enterprise-wide SOA systems are likely to encompass heterogeneous computing environments; therefore, organizations should adopt a standards-based, platform-neutral approach to governance, quality and management, and they should keep interoperability high on their list of priorities.”The suite offers solutions in the following broad categories:
IBM has an advantage over HP in SOA, said Schmelzer, because HP doesn't own a middleware software company. That means HP can provide software and consulting to manage an SOA deployment, but they can't actually run an SOA-based service except by partnering with a middleware provider.But we know from past experience that HP and its own middleware companies tend to mix like oil and water.
Well,
Having had quite some exposure to the systinet webservices stack it has allways been a pleasure to work with, allthough after the mercury take over it seemed that development pretty much stalled. So I havent looked at it recently but maybe I should revisit it again soon.
Leo
I agree: I've been using Systinet (originally Wasp) since 2000 and it's always been great quality. Given my own experience, I'm sure that HP won't let the quality degrade. It'll just be a case of whether they can convince the market they are a serious player and their own salesforce that this is something other than hardware that will make money.
I have serious doubts that HP would care about the Systinet Servers (for Java and C++) - it's sad because they were (and probably still are) great products, but the focus is very, very obviously on the governance tools.
I agree with Stefan. It is too bad these products ended up at HP. HP will look at their books, see that they're making the most money on their printers and this area will either end up underfunded or scrapped.
The refocusing is already happening. They have shut down the systinet forums. It doesn't look like there is a plan to reopen them (i hope i am wrong).
"Effective immediately we will close the online forums at systinet.com.
This is part of our ongoing migration of SOA online community activities to HP.
We will continue to provide product support, tutorials, whitepapers and webcasts at our website, and at www.hp.com/go/soa ."
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.
5 comments
Watch Thread Reply