Mobile Backend as a Service (MBaaS) Blog

The Developer’s Guide to Amazon Web Services for #reinvent

Dev's Guide to AWS

Today Kinvey released our latest free eBook: The Developer’s Guide to Amazon Web Services (or Other IaaS Providers). Given the frenzy of Twitter activity surrounding #reinvent, we thought this would be an ideal time to share this beefy collection of best practices for any developer looking to build or move their application to an Infrastructure as a Service provider such as  Amazon Web Services. After all, IaaS can save developers lots of time, money, and effort, but it comes with its own set of risks and “gotchas” … so we’ve pulled together original and curated content from the people who know best.

The 4,000 word eBook covers everything from IaaS itself, to vendor selection tips, to how to survive an outage. It also contains some surprising facts about AWS, you know, for your next hacker trivia contest. Following is an excerpt from the eBook. Or you can skip right to the real thing and download it here.

5 best practices for deploying an application on AWS 

Use the right tool for the job.
There are several services within the AWS offering. Alex Handy, Senior editor of SD Times, suggests combining multiple: “For example, try Amazon Relational Database Service for your database, AWS Elastic Beanstalk for your development environment, or Amazon Elastic Map Reduce for your Hadoop cluster and Big Data needs.” Familiarize yourself with these tools before diving in.

Start small.
Start by moving a small project to AWS before your full project is underway. This way you can fully test and learn about the various components that you’ll be using without worrying about managing an entire project.

Start free.
Consider starting with Amazon’s free tier to test and become familiar with the platform before jumping into a full development effort. You get 5GB of storage free for a year on S3, so you can easily back something up for free to see if AWS is the way to go.

Leverage multiple availability zones.
If you want your app to be fault-tolerant, mirroring across availability zones is key for high availability and disaster recovery. Ensure your design anticipates and manages component failure to significantly reduce the chances of it failing.

Design for failure and nothing will fail
Understand Amazon’s disaster recovery principles, and always have a backup plan in the event of an outage.

We’ve just compiled an eBook geared for developers reviewing their options for creating or migrating an application to an IaaS provider, and contains information to help you decide:

  • Is IaaS right for my app?
  • What IaaS provider should I use?
  • What criteria are most important to making my decision?
  • Best practices for deploying on IaaS
  • Guides on managing and recovering from IaaS outages
let's talk about this computer

Starting a new mobile project? Check out our App Cost Estimator for a price quote.

comments powered by Disqus