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 Alex Blewitt on Oct 03, 2011
Today, on the one-year anniversary of the purchase of BitBucket, Atlassian announced that BitBucket will be offering Git repositories, as well as their long-supported Hg repositories.
The blog is clear that this does not represent a shift away from Mercurial; rather, as Google Code decided to support Git earlier this year, that there are preferred version control systems for individuals. In order to capture a wide a market share as possible, Atlassian felt that BitBucket had to get into the Git repository hosting (as well as Subversion) in order to make an impact in the DVCS world.
Repositories created in BitBucket have the choice of whether they will be Hg backed or Git backed. There is currently no conversion tool which can be invoked by the repository at this time; however, there are import tools that can consume from a remote Svn, Git or Hg repository. This could permit repositories hosted at BitBucket to be imported from a different repository backing type.
Atlassian hope this will be able to make a dent in with the million GitHub repositories, a milestone reached in July 2010, and (more recently) the one millionth user of the service. (GitHub reached 100,000 users in July 2009.) At the time of the acquisition (September 2010), BitBucket boasted 60,000 users but no public data has been released since then.
It's clear that distributed version control systems are the future, and that BitBucket is a place which can host you project, what ever your preferred distributed version control system is.
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
Continuous Delivery: Anatomy of a Deployment Pipeline
Adopting Git for the Enterprise: Risks and Considerations
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
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