Here’re seven best practices you need while migrating your applications to AWS amazon cloud.
- Design for failure and nothing will fail.
- Implement elasticity.
- Leverage different storage options.
- Build security in every layer.
- Think parallel.
- Loose coupling sets you free.
- Don’t fear constraints.
The seven AWS best practices
1. Design for failure and nothing will fail.
One rule of thumb to keep in mind when designing architectures in the cloud is to be a pessimist; that is, assume things will fail. In other words, always design, implement, and deploy for automated recovery from failure.
An application in cloud design such a way that it should fail. Don’t be foolish. The reality is after its failure if you can able to recover it or not. That’s ultimate matter.
2. Implement elasticity
Some of the best things you can implement with this Elasticity are – services on demand, building of Auto scaling features, design of Stateful/Stateless applications, Bootstrap instances.
3. Leverage different storage options
There is no standard fit of model for storage options. But you can leverage variety of storage options.
Some of those are
- Amazon S3
- CloudFront
- Amazon EBS
- Amazon RDS
One Size Does Not Fit All
| Sample Scenario | Storage Option |
|---|---|
| Your web application needs large-scale storage capacity and performance. | |
| -or- | Amazon S3 |
| You need cloud storage with high data durability to support backup and active archives for disaster recovery. | |
| You require cloud storage for data archiving and long-term backup. | Amazon Glacier |
| You require a content delivery network to deliver entire websites, including dynamic, static, streaming, and interactive content using a global network of edge locations. | Amazon CloudFront |
| You require a fast and flexible NoSQL database with a flexible data model and reliable performance. | Amazon DynamoDB |
| You need reliable block storage to run mission-critical applications such as Oracle, SAP, Microsoft Exchange, and Microsoft SharePoint. | Amazon EBS |
| You need a highly available, scalable, and secure MySQL database without the time-consuming administrative tasks. | Amazon RDS |
| You need a fast, powerful, fully-managed, petabyte-scale data warehouse to support business analytics of your e-commerce application. | Amazon Redshift |
| You need a Redis cluster to store session information for your web application. | Amazon ElastiCache |
| You need a common file system for your application that is shared between more than one Amazon EC2 instance. | Amazon Elastic File System (Amazon EFS) |
4. Build security in each layer
AWS assets are programmable resources, your security policy can be formalized and embedded with the design of your infrastructure.
With the ability to spin up temporary environments, security testing can now become part of your continuous delivery pipeline.
Solutions Architects can leverage a plethora of native AWS security and encryption features that can help achieve higher levels of data protection and compliance at every layer of cloud architectures.
5. Think parallel
As a AWS solution architect you need to use techniques of Multi-threading, Parallelization in each layer.
The beauty of the cloud shines when you combine elasticity and parallelization.
The next thing is you can automate both Multi-threading and parallelization.
6. Loose coupling sets you free
IT systems should be designed in a way that reduces interdependencies, so that a change or a failure in one component does not cascade to other components.
In Amazon cloud this is the best practice you need to follow.
7. Don’t fear constraints
You should not be afraid and constrained when using cloud resources because even if you might not get an exact replica of your on-premises hardware in the cloud environment, you have the ability to get more of those resources in the cloud to compensate.
As the cloud model is to serve on-demand resources. Don’t fear more about small constraints. You will get much better sophistication here.
Related Posts
Srinimf 