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 23, 2012
Amazon has announced Simple Workflow Service (SWF), a service for orchestrating distributed and fault-tolerant tasks that are part of a workflow implementing a business process. Are the recently announced DynamoDB and SWF pieces of a bigger puzzle suggesting Amazon’s entering into PaaS cloud computing?
Amazon has announced the availability of a new service for building and running coordinated, distributed and fault-tolerant applications called Simple Workflow Service (SWF). The idea is to coordinate synchronous or asynchronous tasks constituting a workflow and running them in the cloud or on premises. SWF helps with executing various activities that may reflect a business process or are related in some way.
Amazon SWF makes use of several concepts:
The user has the possibility to write the worker and the decider code in any language. The decider can run anywhere, including a desktop computer, instructing the SWF to execute the actions in a specific sequence and under certain conditions in order to carry out a workflow. SWF keeps tracks of workers’ progress and saves their state, providing the possibility to know what every worker is doing, how it completed its job, and what the results are.
There can be many uses for SWF. For example, NASA is using Amazon SWF for processing images received from Mars Rovers. Processing orders could be another example.
Many companies -Google, VMware, IBM, Microsoft, RedHat, Engine Yard, and others - are investing heavily in Platform-as-a-Service, the PaaS model being considered the future of cloud computing. Amazon, the largest cloud player is still a IaaS provider, but seems to be making steps into the PaaS direction. Firstly, it was Beanstalk, a development and application container for AWS, then it was DynamoDB, a NoSQL database running in the cloud. Krishnan Subramanian, a cloud computing analyst, wondered if DynamoDB was a step towards PaaS when Amazon announced the service in January:
I am completely clueless on where Amazon is going but if Amazon has a plan for PaaS (which I am sure they have because PaaS is the future of Cloud Services), DynamoDB is the first step for them to enter the game in the next iteration of PaaS.
The introduction of Amazon SWF made Subramanian express his conviction that indeed Amazon is preparing to enter into the PaaS game:
If DynamoDB was the first step to building next gen platform service, today’s release of Simple Workflow Service is the next critical piece to the puzzle. This powerful orchestration tool could turn out to be the most powerful part of Amazon next-gen platform toolkit.
If anyone thinks after today’s announcement that Amazon has no clue for the future dominated by PaaS, I think they are fooling themselves. By now, it is pretty obvious how Amazon is approaching the platform game and with this announcement, they are clearly showing their cards. Game on!!
It remains to see if Amazon is indeed getting up to speed for a full-blown PaaS offering, but chances they are. They are known for releasing features one by one as they are ready, so DynamoDB and SWF seem to be intermediary steps preparing Amazon’s entry into the PaaS market.
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