Ntier architecture
- Overview

- BCDR (Business Continuity and Disaster Recovery):

- Elasticity: To support peak demands or variable demands, we need to scale out (increase) the servers and when the demand hits normal limits scale in (decrease).
General Configuration Details
- Public ip’s are required to serve connectivity from any where
- All of the servers will be deployed within a private network
- Necessary servers will have public ip
- Steps:
- Create/use the private network. Ensure this private network can connect to internet
- Some subnets should have an option to have public ip connectivity.
- Create a database
- Create the app server
- create the web server
- Private ip has reserved ip ranges

- On the cloud we are supposed to choose the region(s) first. Generally low latency from actual usage locations.
- Cloud has Database as a service.
Ntier in Azure
- Create a resource group



- Create a virtual network in the resource group created
- Add 3 subnets
- Data
- Application
- Web Subnet




-
Create an Azure SQL Database (with connectivity to Data Subnet)





-
Create a ubuntu vm in Application subnet
- Install some softwares


- Install some softwares
- Create a ubuntu vm in Web Subnet
- Install some softwares


- Install some softwares
Ntier in AWS
- In AWS we can create a vpc (Network) or use default vpc
- In this demonstartion we will be using a default vpc

-
For database we will be creating a free tier eligible AWS RDS for mysql







-
Ubuntu EC2 instance in one subnet (application)
- No public ip




- No public ip
- Ubuntu EC2 instance in one subnet (web)
- public ip




- public ip
