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 Abel Avram on Jan 14, 2011
A Gartner webinar (PDF) compares three major players in the software industry today - Apple, Google and Microsoft –, trying to see where they stand today, and how IT decisions will be affected by their competition with each other. TheOpenSourcery compared the same companies from a different perspective: agility and openness.
Tom Austin, VP & Gartner Fellow, and David Mitchell Smith, VP & Gartner Fellow, have held a webinar (PDF) entitled “Google vs. Microsoft: The Battle for Future Dominance (and Apples Sneak Attack)” (registration required), comparing Apple vs. Google vs. Microsoft, what are their main characteristics, the financial present status and future prospects, how they are seen in the enterprise, how their main products compare with each other, and how IT decisions will be influenced by the confrontation between these companies.
Tom Austin emphasized the following characteristics about Apple:
About Google, Tom Austin said among others:
David Mitchell Smith said about Microsoft:
According to Austin and Smith, both Microsoft and Google are doing well financially, but none of them is growing, so they are looking for opportunities for growth. While Microsoft wants a share of the search and ads business, and another in cloud computing, Google’s plans are not so predictable. They have built an entire array of tools – Chrome, Check-out, Analytics, YouTube, Search, GMail, etc.-, and they have access to a large amount of people’s data – IP, location, search history, websites visited, videos watched, tweets, etc., leading the Gartner analysts to think how Google could monetize the “democratization of information” by using “social and demographic trends, behavioral targeting, implicit social profiles, personal preferences”, all using “creeping details” of users.
Apple’s story is different because they have had strong growth for the last few years. The iPod, iPhone and iPad are all showing signs of health and creating increasing profit for the company.
Following is Gartner’s study on how enterprises perceive these three companies:
TheOpenSourcery compared Apple, Google, and Microsoft from a different point of view, software development agility and openness as perceived from the outside. Apple is seen as secretive, with long-term iterations, but with the ability to react swiftly if necessary:
Apple – general directions but no declaration of the overall plan’s detail and steps. Rather the opposite, those details are kept ultra-secretive. Thus testing and co-designing with clients and customers is also kept ultra secretive. The cycle for major updates is generally one year but Apple can deliver in considerably less time a major upgrade or fix as has been seen in the iPhone and iPad in recent times.
Google gets a mixed review: sometimes is very open, and sometimes can be secretive as Apple:
Google – also provides general directions and has introduced and then after 1- or 2 iterations walked away from, redirected, or postponed work on major projects. Two examples are Google Wave and the Nexus One Smartphone. Google has a mixed record on being open about the detailed plan; some projects are explicit and others are as secretive as Apple. However, once a basic API is revealed, the project becomes more open. Often clients are invited early to do beta testing [think Google Books and Google Maps] and are surveyed for their reactions to the software. The projects tend to have short update cycles of 3-6 months [think Android and Google Docs] but this may be after a longer 1 year or greater first gestation period.
Microsoft is sometimes open and has long development cycles:
Microsoft – also provides strategic planning and directions. Its Windows continuum was renewed once again by Steve Ballmer at the CES 2011 show with one significant departure – instead of being exclusively an Intel x86 platform choice, Microsoft has added the ARM CPU+System architecture. But the OS will be Windows 7 not Windows Phone 7 [which is built on largely the same language tools but has some novel OS design and implementation methods].
Like Google, Microsoft can be mixed on how the detailed plan is implemented – sometimes open and other times ultra secretive. But Microsoft almost always has a substantial beta processes sometimes eliciting the participation of thousands of users and some prestigious early client/organizational adopters. However, Microsoft software generally has very long delivery cycles measured in years. Typical is the recent Windows cycle which from XP to Vista was 4-5 years and Windows 7 to Windows 8 looks like 2-3 years. Even the Windows 7 upgrade for from Vista to 7 was well more than a year. Even for smaller software projects like the IE browser the Microsoft development cycle is very long: IE6 to IE7 took 6++ years. Even after Bill Gates promised a faster update cycle after IE7, IE8 took 2++ years, IE9 appears to be keeping that same 2 year cycle.
Each company has its strengths and weaknesses. They are all going to be around for a long time, but it is pretty hard to predict their evolution. If one chooses to go either with Apple, Google or Microsoft, a good advice is to avoid vendor lock-in if possible.
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
RDBMS to NoSQL: Managing the Transition
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!
Seems to be Kinect and Surface are interesting emerging devices.
I'm confused. Why is Apple included in a presentation targeted at companies looking to invest or have already invested in cloud computing ("Why are you listening today?")? The summary above mentions rumors of an Apple "cloudy data center", but I don't see that in the actual report. It seems more like someone wanted to compare the foreseeable future of these three companies and cloud-computing was shoved in as an afterthought.
The comparison grid captured above is itself hard to interpret. What does "cool-aid" mean, for example? Some of the comparisons feel like they're looking at different things. They might as well describe the three as "green, spicy and extra-large".
Openness: "Aggressive"?
The comparisons are interesting and sometimes funny by themselves, but I would have expected some insights, predictions or conclusions drawn from that data.
One obvious trend I see is integration, but PC's and telephones have been doing that forever. What's interesting is that these big companies are targeting each other on turf previously owned by the other. This isn’t just these 3 but also Cisco, Oracle/Sun and some others are also spending tremendous energy and resources are innovating the products we use. It’s seems they are trying to become a one stop shop company for customers.
I used to fear those huge monolithic companies because of them trying to monopolize the market by not supporting standards sabotaging multi-platform development, ultimately achieving vendor lock in. But not supporting standards would spell certain doom with customers nowadays and not being open about once platform would result in little third parties releasing anything and thus a very unattractive platform.
The numbers game has changed for these companies. Computers would sell in the millions, but nowadays smart phones sell in the billions. With tablets and clouds coming, there is a huge market on the horizon. Even with a small percentage of that market and a relatively low margin on their products a company may reap huge profits.
I suppose these big companies will be more like a supermarket than a car maker. Car maker sells their cars at bottom price and upsell their accessories ridiculously overpriced. The supermarket sells everything at bottom price and doesn’t care where you pick up your other groceries, just as long as they’re able to sell in volume.
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.
3 comments
Watch Thread Reply