Scaling the project with Amazon Web Services
Tags: aws, scaling, devtips, webdev
Published: 2017-10-10 14:36:09

---
layout: post
title: "Scaling the project with Amazon Web Services"
published: true
tags: aws, scaling, devtips, webdev
cover_image: "https://thepracticaldev.s3.amazonaws.com/i/kpnwidq16omhvzwv2qoi.jpg"
---

<h3>Amazon Web Services</h3>
 

AWS is a cloud services platform that provides a variety of infrastructure services including cloud computing, access to database and data storages, and other functional capabilities, that help app developers to successfully scale their applications.

When using cloud computing you have a lower cost comparing to in-house calculations. Since thousands of customers consume resources in the cloud together, </span><a href="https://aws.amazon.com/?nc1=h_ls"><span style="font-weight: 400;">AWS</span></a><span style="font-weight: 400;"> can achieve high economies of scale, helping organizations reduce expenses for using resources.

 

<h3>Scaling the project: Scenarios</h3>
 


<b>1 User<b>
 
In this case, you need only one user. To build the architecture you should run on a single database, for example, a type t2.micro.

The types of instances include various combinations of CPU, storage, memory, and networking capacity, providing app development teams with the flexibility to choose the optimal resources’ combination.

With a single instance, you will be able to run the entire web stack, including (for instance) a web application, database, management, and so on.

Then, for the Domain Name System (DNS) it’s better to use Amazon Route 53, a highly available and scalable cloud-based web service for the DNS.

The Amazon Route 53 service is used to connect only to “healthy” addresses  (using DNS checks) and to independently monitor the status of the application and its endpoints.

 

<b>>10 Users; >100 Users</b>
 
Use one host for the future website. Separate out a single host into multiple ones as the use of the separate hosts will enable both website and database to be scaled and failed independently of each other.

Also, use one host for the database. Start with a SQL database and move to NoSQL only if necessary. You should start with NoSQL, when:
 

- You have a super intensive data workload.
- You don’t have any relational data.
- The project requires a high throughput.
- The requirements for your future application are very low-latency.
- The system needs storing > 5 TB of data in the first year.


To scale your web project to over 100 users use a separate host for the web tier and store the database on the Amazon Relational Database Service (Amazon RDS).

Amazon AWS is a web service that simplifies the process of setting up, operating, and scaling a relational database in the cloud. Also, Amazon RDS enables to manage common database administration tasks.



Learn more about <b></span><a href="https://smartym.pro/blog/software-project-development-how-to-scale-your-application-with-amazon-web-services/"><span style="font-weight: 400;">project scaling with AWS up to millions of users.</span></a><span style="font-weight: 400;"></b>

To start, check out </span><a href="https://aws.amazon.com/documentation/?nc2=h_ql_d"><span style="font-weight: 400;">AWS documentation.</span></a><span style="font-weight: 400;">