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 Feb 25, 2011
Microsoft has made available a kit for streamlining the process of deploying Java applications to Windows Azure.
Until now, to run a Java application on Windows Azure, the deployed package needed to contain configuration information for a Worker Role, which required updating the service definition file, setting some attributes in the service configuration file and creating a .NET class to handle the Role’s lifecycle. A MSDN webpage gives detailed explanation on how to deploy a Java application on Azure. The process is not a point-and-click one, requiring the creation of a C# class in Visual Studio, a .NET library for handling Zip files, and editing Azure service configuration information.
Microsoft has made the job of deploying Java apps easier by releasing the Windows Azure Starter Kit for Java, a zip file containing a template project and an Ant extension. The kit can be used as a stand alone tool from the command line, the main element being the Ant build file that creates all the necessary files (example), or it can be used from Eclipse which invokes the Ant file when the project is built (example).
By editing a configuration file, the developer can choose to deploy the application locally for testing purposes, or in the cloud. When the later option is selected, the kit generates the files .cspkg and .cscfg needed when deploying to Windows Azure.
The Starter Kit is a CTP, Microsoft being interested in getting “feedback from Java developers, and to nail down the correct experience for Java developers, particularly to make sure that configuring, packaging and deploying to Windows Azure integrates well with common practices.” The kit has been released under the Apache 2.0 license.
Troubleshoot Java/.NET performance while getting full visibility in production
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Banking Case Study: Scaling with Low Latency using NewSQL
Tools to unit test your JavaScript
Introducing SQLFire: a memory-optimized, high performance SQL database
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
After GAE-java & vmforce, now it is microsoft's turn to woe java developers to their PaaS.
Everyone under the "sun" is claiming java application development in cloud. While the owner of "sun" seems to be cloudy about java on cloud!
you missed Amazon elastic beanstalk amongst the "woers" list :-)
Beautiful words Mani.
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