Tuesday, December 2, 2014

Cloud System Architecture Examples

Here are a few architecture examples to follow up our last post about cloud computing considerations.

Single Instance Solution

This is the bare minimum requirement to be able to serve a handful of websites or applications to your users. If you aren't anticipating a large amount of traffic or requests, this might be more than enough. You'll be able to set up, for example, a Linux distribution, Nginx, and Mongo database, all on the same server. While there are a good number of affordable options in this category, keep in mind, they can be very limited.

As you install more software to your server, you'll start to notice anomalies as you run out of resources. You'll have to allocate more processing power, memory, and cores, which means an increase in cost.

Multi-tier Solution with Redundancy

As traffic to your application increases, you'll need to start implementing redundancies. Multiple servers allow you to handle more load, and database replication maintains the integrity of your data. You'll also need to install load balancers to distribute traffic across nodes and properly route requests in case of an outage.

Multi-Zone Solution with Redundancy

A zone can be considered a data center or a region. Either way, it helps to install redundancy across these as well, not just in case of outages, but to ensure that latency for customers in distant locations isn't decreasing too significantly.

That concludes this article. I'll continue to provide diagrams for different scenarios, in the future. Some of these will take autoscaling, caching, or queues into consideration. Others will drill down into how to leverage solutions like Redis, Memcached, Membase, Hadoop, or Cassandra into your design. Check back, soon.

No comments:

Post a Comment