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 Dec 06, 2010
Amazon is offering a new cloud service called Route 53 providing all the functionality needed to run a DNS server in their cloud without any maintenance overhead and using the pay-as-you-go model common to all AWS services.
Route 53 is a new Amazon Web Service for managing DNS names and answering DNS queries. The service provides the functionality of a DNS authoritative server running inside Amazon’s cloud and being accessed through a REST API. The API allows an user to create and manage zones and to populate them with DNS records. When a zone is created, the service also creates 4 name servers answering queries for the domains defined for the respective zone. Route 53 can be used to serve domains running inside Amazon’s cloud, on-premises or a combination of these.
Amazon attempts to offer a high-availability and low-latency DNS service by providing 9 locations in various states over US, 4 in Europe, and 3 in Asia. Route 53 routes any DSN request to the closest server in order to provide the fastest response. Amazon also promises to provide enough transparent scalability as necessary in order to serve all the DNS queries.
One of the main problems with DNS servers is sometimes the slow propagation of changes. Without specifying how fast Route 53 does the updates, Werner Vogels, CTO at Amazon, mentioned that “We have designed Route 53 to propagate updates very quickly and give the customer the tools to find out when all changes have been propagated.”
The pay-as-you-go model used for other AWS services is also used for Route 53. The fees are applied per zone and per number of queries, Amazon taking care of the infrastructure and administration needed to run the service:
The service allows the creation of 100 hosted zones. More zones can be created after contacting Amazon. The name Route 53 comes from the port UDP 53 used by DNS servers to receive and respond to queries.
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