AWS HLD for a web service

Designed by Terry YangMin Kim

 

 

1.Purpose

The purpose of this document is to provide INITIAL high-level design(HLD) of a project.

 

 

2. Architecture summary

It has four groups for EC2 and RDS and File Storage (EFS) and a Bastion host.

* RG group is in the future.

 

2.1 Initial Architecture

This is for initial architecture before auto-scale out.

 

2.2 Scale-out Architecture

The Scale-out will expand each EC2 group to another AZ.

 

 

3.1 Interface(I/F) Group

Property : Linux instances with auto-scale
Needed performance : CPU
Role : 
 a. Receiving files(.stf2) on HTTP(s) from users via internet
 b. Analysis
 c. Distribute files(.stf2 & .csv) to Storage group
 d. Distribute analyzed files to DB

 

 

3.2 WAS Group

Property: Linux instances with load-balance

Role :

 a. Allowing access to tomcat from users via the internet

 b. Connecting DB and Storage group

 

3.3 Pattern Generator(PG) group (UNIQUE)

Property : Window instances with auto-scale

Needed performance : GPU

Role :

 a. generating UNIQUE patterns

 b. connecting DB and Storage group

 

3.4 Storage Group

Property: EFS, Linux instances with load-balance

Role :

 a. Available for connecting I/F, WAS, PG group to HTTP

 b. Available for zero-time scale up or out

 

3.5 Database

Property: Maria DB

Role :

 a. connecting I/F, WAS, PG groups

 b. Available for HA (AZ backup)

 c. Available for Cluster (Read-only replica)