6 Important Laws Of Architecture For AWS Cloud
Amazon announces a bunch of surprises at its annual cloud conference every year, and this year was no different. At the AWS re:Invent 2015 conference, Amazon CTO Werner Vogels shared his set of 6 important laws of architecture for AWS Cloud that AWS Architects, Developers and Customers should know in order to create, maintain and sustain efficient cloud infrastructures.
These laws will surely guide you to see things differently and make the right choices and create efficient architectures with the power of AWS.
- Lucas Critique
We really can’t predict what the future will hold for the IT landscape. But what’s certain is that there will be a need of interconnectivity where businesses can connect with users, apps, locations with greater proximity and the data transfer needs to be flexible, agile and faster than it is today.
To support this statement, Werner introduced Amazon Kinesis Firehose, a simple & highly scalable data ingestion tool that provides time stamping for real-time streaming data, to make it easier to extract insights.
- Gall’s Law
It all starts with simple things in place. Start to build with simpler systems that have basic functionalities, test them out, fix and learn from the errors if any. Only then you can constructively build better systems.
On that note, Amazon launched the massive X1 EC2 instance type with 2TB of memory and the new t2.nano instances that give developers the access to a single virtual CPU and 512MB of memory and aims to better power simple systems. The new X1 EC2 instances are high-memory instances designed for in-memory databases such as SAP HANA as well as memory intensive and latency sensitive workloads such as Microsoft SQL Server, Apache Spark, and Presto, whereas the t2.nano instances are designed for workloads that often don’t require a heavy load but sometimes have to burst up to handle more work.
- Law of Demeter
Better interconnectivity between systems is what most clients look forward to. So, design an application that is modular, has better interconnectivity and is simple to use where you can easily add/swap components whenever you want.
Werner introduced the Amazon Mobile Hub that promises to give developers the flexibility to build apps focusing only the functionalities that they want to deliver.
- Occam’s Razor
While architecting any system you should look out for ways that will only lead you to success than counting on assumptions which may lead you to darker routes. Solutions with minimum number of assumptions reduces the way you can be wrong.
Supporting this Werner introduced QuickSight, an intelligent BI tool which will help AWS customers to visualize their data within 60 seconds. Using QuickSight users can take more informed decisions with fewer assumptions!
- Reed’s Law
As you scale up, you grow. The growth of your network is directly proportional to your strategic approaches to succeed. Be scalable.
On that note, Werner introduced Amazon IoT that lets connected devices easily and securely interact with cloud applications and other devices. It allows organizations to securely connect and manage devices at any scale.
- The Gestalt Principle
Vogels shaded some light on the importance of partnerships and how “we couldn’t do this alone.” By collaborating, we can achieve more and do more. Glad, our parent company have been announced as the AWS Premier Consulting Partner, second time in a row this year!
And in the end, in a lighter vein, Vogels insisted to practice Beastie’s Law:
“You’ve got to fight for your right to party!”
Having learned these basic laws we hope that you will start creating more efficient cloud architectures.
How have you appreciated these laws? Tweet to us. We would love to hear it from you.
You can also read about the 4 Pillars of AWS Architecture provided in a whitepaper published by AWS during re:Invent.