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 Jean-Jacques Dubray on Aug 08, 2010
In 2007, Microsoft first discussed publicly its plans for “Oslo” — an amorphous multi-product effort that encompased future releases of .Net, Visual Studio, BizTalk and SQL Server. By the fall of 2008, Microsoft had decoupled .Net, VIsual Studio, BizTalk and SQL Server from Oslo. When officials said Oslo, they meant Microsoft’s evolving modeling strategy and technologies, specifically the M language, the Quadrant tool and the associated metadata repository.
In the summer of 2009, as part of one of Microsoft’s countless reorgs, the Oslo team was combined with Microsoft’s Data Programability team (which manages Astoria, Entity Data Model (EDM), Entity Framework (EF), XML, ADO.Net and tools/designers).
She explains:
Multiple contacts of mine are telling me that Microsoft has decided to shelve Quadrant and “refocus” M.
A Microsoft's spokesperson was quoted:
“We are still working on SQL Server Modeling and it remains an important part of our Data Platform strategy. Our current plans are to ship our modeling platform in a future release of SQL Server/Azure. Customers can download the latest CTP which we have updated to use the VS 2010 and .NET 4 to give us feedback.”
Ever since it's inception, the project endured major rescoping without ever emerging from a CTP status. With Microsoft presiding at the future of UML, the moderate success of the Software Factories, and the rapid growth of Eclipse as a strong Modeling platform, one can only wonder what strategy will Microsoft adopt in the Model Driven Engineering (MDE) space. What's your take on it? Where is the future of MDE? How can Microsoft participate in that future?
Automating Error Reporting for .NET Applications
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Troubleshoot Java/.NET performance while getting full visibility in production
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!
Middle management, hype, reorganization, politics...together they seem to have created a situation where only a fool would get excited about any announcement of anything new from Microsoft. Personally I am more sad to see what they have done to IronRuby as it showed real promise, Oslo showed a little promise but it quickly turned out ot be nonsense.
Sounds like Microsoft drops another innovative project while spending time on small pocket-size CASE-constructor projects like WebMatrix and LightSwitch probably oriented on housewives. Oslo was ambitious and hard to implement, though it could bring DSLs to masses.
While we keep hearing that semantic web is "real soon now", I do believe that we are approaching a time when ontology based approaches will start to gain real traction.
Some recent indications are:
- Google purchase of Metabase
- IBM's 'Smart Plant' initiative
- Many emerging products around text mining and natural language processing
if by real soon, you mean in another 15 years, then I would say yes. semantic web has been around for 10 years now with very little progress and tons of failures. Just look at all the semWeb startups that failed miserably. I like ontology approach and feel it's quite powerful. Done properly for a focused problem, it works well. What W3C is pitching as semantic web on the other hand is junk.
Isn't the real problem with the semantic web that it requires everyone agree on the semantics? (so to speak)
Without a single (accepted) authority making that determination, you basically have to wait for a spontaneous mass adoption of a single standard (ala Facebook.) History has shown that this often means that the best option is not chosen.
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