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 Srini Penchikala on Jan 13, 2012
After six years of gestation, open-source distributed computing and Big Data framework Apache Hadoop 1.0.0 was recently released. Core features in the new release include:
Other features in the new release include some performance enhancements, bug fixes, and features.
InfoQ caught up with Arun Murthy, VP of Apache Hadoop Project, about the features in 1.0.0 release and what features will be included the next release.
InfoQ: Apache Hadoop 1.0.0 was released after six years of development work. Why it took so long for the first release?
Arun Murthy: Apache Hadoop is already used in production environment at several large enterprises such as Yahoo, Facebook etc. The 1.0.0 moniker is more of a statement from the Apache Hadoop community that the release is a indeed mature one and is something the community is confident of supporting in a compatible manner for the foreseeable future for a wide variety of use cases in various enterprises. This should increase confidence of end-users and enterprises and aid further adoption of Apache Hadoop.
InfoQ: What type of security features does this release support, in terms of authentication, access control and data encryption?
Arun: 1.0.0 supports strong, end-to-end Kerberos based authentication for both HDFS (filesystem for storage) and MapReduce (data processing). Kerberos is by far the most popular network authentication protocol used in the enterprise.
It also provides strong access control at all levels for applications and data. For example, one can ensure that only a certain individual (or set of users) can view running applications, see application logs etc.
InfoQ: Can you discuss the performance enhancements made in the new release?
Arun: There are several enhancements. A prime example is the local-read optimizations we have done for applications like Apache HBase which provide significant boost (2x in certain cases).
InfoQ: What are some new features you are planning on releasing in the next version of Hadoop?
Arun: The next major release of Apache Hadoop is currently in alpha stage and expected to be released by middle of 2012. Some major highlights are:
Arun also said that they feel the next version of Apache Hadoop significantly improves Hadoop with many enterprise grade features such as High Availability and allows Hadoop to be used in even wider variety of use-cases (i.e. NextGen MR aka YARN) in the enterprise.
Srini Penchikala currently works as Security Architect and has 17 yrs of experience in software product management.
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