A couple of years ago I came across the video of a presentation that some young Japanese Solution Architects from AWS hosted at re:Invent 2012. They were presenting architectural solutions in the AWS through a series of Design Patterns.
I found it extremely interesting, because I work in the Cloud Computing industry since years, and many of the traditional concepts of Design Patterns are very resonant with the potentials of the cloud. For example: drawing an architectural solution starting from common needs in the whole range of architectures computer systems, or automating predetermined layouts, specific actions based on events, and so on. To test the reception of the academic and professional area on this topic, I hosted a talk on this topic in July 2013, during the Cloud Community Day, an event I organized with EuroCloud Italy in the Politecnico of Milan, a prestigious Italian university.
The topic is quite broad, so we will have discussed in a series of posts, starting with this one. Don’t mean to be exhaustive, but hope to inspire you the curiosity shared by many other Patterns enthusiasts.
The concept of AWS Cloud Design Patterns
A good, general definition of a Design Pattern might be as follows: “A general reusable solution to a commonly occurring problem”. A design pattern is defined by the following elements:
- a Name for the Design Pattern;
- a description or a model to be applied to solve a problem that can occur in different situations during the design process;
- a problem, or the description of the situation you can apply the pattern too;
- a solution describing the elements of the project with the relations and their consequences;
- the consequences, results, and constraints resulting from the application of the pattern.
It’s important to remark that, given the rapid innovation of the Cloud services, a design pattern may become obsolete over time, for example, due to the release of new services. For example, think to Lambda, the new service that AWS recently launched: it could replace many architectural solutions. Or the new RDBMS service called Aurora: it might become a better solution for RDS on AWS than other engines. It’s important to stay up-to-date with news like these and update your Design Patterns accordingly.
AWS has no reference nor official documentation about Cloud Design Patterns but they have a good amount of continuously updated “Best Practices” documents available at the AWS Architecture Center. Also, they share a good amount of Whitepapers that you might want to read. The AWS blog is another place where you can often find many interesting pointers. None of them is primarily focused on Cloud Design Patterns though. So, all in all, this initiative by the three Japanese guys, who work for AWS since several years, by the way, seems to be an unofficial effort, probably born as a great evangelizing activity aimed at creating a community of pattern designers.
On the implementation side though, AWS has a service that perfectly blends with the logic of Cloud Design Patterns, and it is Cloud Formation. A solution described by a Design Pattern may be easily transformed into a template of CloudFormation. An interesting software from an AWS partner, that is Cloud Pattern Studio, tries to do just that. It’s a free AMI, published on the AWS Marketplace and produced by Cognizant, which allows you to draw an environment in AWS and to export it as a template of Cloud Formation.
Now, a definition for AWS Cloud Design Patterns might be as follows: “AWS Cloud Design Patterns are a collection of solutions and design ideas aimed at using the AWS Cloud technology to solve common systems design problems”. Following up the breakdown we have seen before, a Cloud Design Pattern might be described as follows:
- Pattern Name/Summary: Pattern name, summary, and a brief description;
- Solving Issues: Description of typical issues that led to pattern creation, and what issues/challenges can be solved through its implementation;
- Explanation of pattern / Resolution in the cloud: Description of the terms or how to solve the problems in the cloud; why any pattern or a description of the configuration has become a pattern of what;
- Implementation: Description about how to implement the pattern using AWS;
- Benefits: Description of the benefits from the pattern’s application;
- Notes: Description of tradeoffs, advantages, disadvantages, and points to note when applying this pattern;
- Other: Comparison with other patterns, use cases, and additional information.
In the next post, we will see an application of these patterns to a practical use case, to have a better idea of how Cloud Design Patterns can help you design effective architectures in real-life scenarios.
What Exactly Is a Cloud Architect and How Do You Become One?
One of the buzzwords surrounding the cloud that I'm sure you've heard is "Cloud Architect." In this article, I will outline my understanding of what a cloud architect does and I'll analyze the skills and certifications necessary to become one. I will also list some of the types of jobs ...
Content Roadmap: AZ-500, ITIL 4, MS-100, Google Cloud Associate Engineer, and More
Last month, Cloud Academy joined forces with QA, the UK’s largest B2B skills provider, and it put us in an excellent position to solve a massive skills gap problem. As a result of this collaboration, you will see our training library grow with additions from QA’s massive catalog of 500+...
DevSecOps: How to Secure DevOps Environments
Security has been a friction point when discussing DevOps. This stems from the assumption that DevOps teams move too fast to handle security concerns. This makes sense if Information Security (InfoSec) is separate from the DevOps value stream, or if development velocity exceeds the band...
Test Your Cloud Knowledge on AWS, Azure, or Google Cloud Platform
Cloud skills are in demand | In today's digital era, employers are constantly seeking skilled professionals with working knowledge of AWS, Azure, and Google Cloud Platform. According to the 2019 Trends in Cloud Transformation report by 451 Research: Business and IT transformations re...
Disadvantages of Cloud Computing
If you want to deliver digital services of any kind, you’ll need to estimate all types of resources, not the least of which are CPU, memory, storage, and network connectivity. Which resources you choose for your delivery — cloud-based or local — is up to you. But you’ll definitely want...
Google Cloud vs AWS: A Comparison (or can they be compared?)
The "Google Cloud vs AWS" argument used to be a common discussion among our members, but is this still really a thing? You may already know that there are three major players in the public cloud platforms arena: Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP)...
Deployment Orchestration with AWS Elastic Beanstalk
If you're responsible for the development and deployment of web applications within your AWS environment for your organization, then it's likely you've heard of AWS Elastic Beanstalk. If you are new to this service, or simply need to know a bit more about the service and the benefits th...
How to Use & Install the AWS CLI
What is the AWS CLI? | The AWS Command Line Interface (CLI) is for managing your AWS services from a terminal session on your own client, allowing you to control and configure multiple AWS services and implement a level of automation. If you’ve been using AWS for some time and feel...
Cloud Academy’s Blog Digest: July 2019
July has been a very exciting month for us at Cloud Academy. On July 10, we officially joined forces with QA, the UK’s largest B2B skills provider (read the announcement). Over the coming weeks, you will see additions from QA’s massive catalog of 500+ certification courses and 1500+ ins...
AWS Fundamentals: Understanding Compute, Storage, Database, Networking & Security
If you are just starting out on your journey toward mastering AWS cloud computing, then your first stop should be to understand the AWS fundamentals. This will enable you to get a solid foundation to then expand your knowledge across the entire AWS service catalog. It can be both d...
How to Become a DevOps Engineer
The DevOps Handbook introduces DevOps as a framework for improving the process for converting a business hypothesis into a technology-enabled service that delivers value to the customer. This process is called the value stream. Accelerate finds that applying DevOps principles of flow, f...
AWS AMI Virtualization Types: HVM vs PV (Paravirtual VS Hardware VM)
Amazon Machine Images (AWS AMI) offers two types of virtualization: Paravirtual (PV) and Hardware Virtual Machine (HVM). Each solution offers its own advantages. When we’re using AWS, it’s easy for someone — almost without thinking — to choose which AMI flavor seems best when spinning...