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 Ron Bodkin on Jun 29, 2011
Yahoo spun-out its core Hadoop engineering team yesterday with an investment from Benchmark Capital, forming a new company Hortonworks. CEO Eric Baldeschwieler presented the company's vision at a keynote at the Hadoop Summit today - they will sell support, training, and certification primarily in partnership with other companies. Hortonworks is initially focusing on making Hadoop more accessible by simplifying installation and making frequent sustaining releases. Going into 2012, the company will focus on Hadoop 0.23 with its Next Generation MapReduce, improved performance, simplified management and continuing investment to eliminate single points of failure in Hadoop. Baldeschwieler emphasized support for Hadoop, HBase, Pig, and Hive.
Baldeschwieler quoted an analyst organization that they are "seeing Hadoop in all of our Fortune 2000 data accounts." He said that today the technology is hard to use, with a need to hire experts or consultants, so Hortonworks is focusing on plugging technology and knowledge gaps. The company will sell training and support via partners as well as do product development. It won't sell a distribution, but will sell support for the open source distribution.
The company's objectives are to make Apache Hadoop:
In 2011 the company is focusing on:
In 2012 the company is emphasizing:
Baldeschwieler emphasized working through Apache: "All our work is going back into Hadoop, no if's what's or buts" and that they want companies to base their "offering on the Apache offering, anyone who does that is our partner." It's worth noting that Apache recently signaled a more aggressive enforcement of its trademark rules with regard to Hadoop. Baldeschwieler noted that Yahoo is a development partner as well as a customer and investor for Hortonworks - that Yahoo will continue to be central in the release process for Apache Hadoop. He also announced that business operations for the company will be run by its President Rob Bearden, the former COO of both SpringSource and JBoss. In response to a question about the relationship of Hortonworks and Cloudera, He said "That's to be determined. We've been working together to improve Apache Hadoop. In the past we've had our differences, but as I said anyone who's focusing on Apache Hadoop is our partner."
Ron Bodkin is the Founder of Think Big Analytics, which builds big data solutions using Hadoop and NoSQL.
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Big Data, Cloud & Mobile: Navigate the New Development Reality with Resources from IBM
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
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.
No comments
Watch Thread Reply