Multi-tier architecture patterns in AWS - Time & Space Complexity

Time Complexity: Multi-tier architecture patterns

O(n)

Understanding Time Complexity

When building multi-tier architectures in the cloud, it's important to understand how the time to process requests grows as more users or data are involved.

We want to know how the system's work changes when the number of requests or components increases.

Scenario Under Consideration

Analyze the time complexity of handling requests through a typical 3-tier AWS architecture.

// Simplified AWS multi-tier setup
// 1. Client sends request to Application Load Balancer (ALB)
// 2. ALB forwards request to EC2 instances in Auto Scaling Group (App tier)
// 3. EC2 instances query RDS database (Data tier)
// 4. RDS returns data to EC2 instances
// 5. EC2 instances respond back through ALB to client

This sequence shows how a request flows through the tiers to get processed and responded to.

Identify Repeating Operations

Look at what happens repeatedly as requests increase.

• Primary operation: Each incoming request triggers API calls to the ALB, EC2 instances, and RDS database.
• How many times: Once per request, repeated for every user request.

How Execution Grows With Input

As the number of requests (n) grows, each request goes through the same steps.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 ALB + 10 EC2 + 10 RDS calls
100	About 100 ALB + 100 EC2 + 100 RDS calls
1000	About 1000 ALB + 1000 EC2 + 1000 RDS calls

Pattern observation: The total operations grow directly with the number of requests.

Final Time Complexity

Time Complexity: O(n)

This means the work grows linearly with the number of requests; doubling requests roughly doubles the work.

Common Mistake

[X] Wrong: "Adding more tiers will multiply the time complexity exponentially."

[OK] Correct: Each tier adds fixed steps per request, so the total work grows linearly, not exponentially.

Interview Connect

Understanding how multi-tier systems scale with requests helps you design and explain cloud architectures clearly and confidently.

Self-Check

"What if we added caching between the app and data tiers? How would the time complexity change?"

Practice

1. What is the main purpose of using a multi-tier architecture in AWS?

easy

A. To combine all application components into a single server

B. To reduce the number of servers needed by merging databases and web servers

C. To separate an application into layers for better security and scalability

D. To allow direct internet access to all parts of the application

Solution

1. Step 1: Understand multi-tier architecture concept

   Multi-tier architecture divides an app into layers such as web, application, and database tiers.

2. Step 2: Identify benefits of layering

   This separation improves security by isolating layers and helps scale parts independently.

3. Final Answer:

   To separate an application into layers for better security and scalability -> Option C

4. Quick Check:

   Multi-tier = layers for security and scaling [OK]

Hint: Think layers for security and growth, not one big block [OK]

Common Mistakes:

• Thinking all parts should be on one server
• Assuming all components need internet access
• Confusing multi-tier with single-tier or monolithic

2. Which AWS subnet type is typically used to host internet-facing web servers in a multi-tier architecture?

easy

A. Public subnet

B. Isolated subnet

C. Private subnet

D. VPN subnet

Solution

1. Step 1: Recall subnet types in AWS

   Public subnets have a route to the internet gateway, allowing internet access.

2. Step 2: Match subnet to web servers

   Internet-facing web servers need public subnets to receive traffic from users.

3. Final Answer:

   Public subnet -> Option A

4. Quick Check:

   Internet-facing = public subnet [OK]

Hint: Public subnet means internet access for web servers [OK]

Common Mistakes:

• Choosing private subnet which blocks internet access
• Confusing isolated subnet with public
• Thinking VPN subnet is for public web servers

3. In a multi-tier AWS architecture, which tier is usually placed in a private subnet to protect sensitive data?

medium

A. Database tier

B. Application tier

C. Web tier

D. Load balancer tier

Solution

1. Step 1: Identify tiers and their security needs

   The database tier holds sensitive data and needs strong protection.

2. Step 2: Determine subnet placement

   Private subnets restrict internet access, ideal for databases to prevent direct exposure.

3. Final Answer:

   Database tier -> Option A

4. Quick Check:

   Database = private subnet for security [OK]

Hint: Sensitive data stays in private subnet (database) [OK]

Common Mistakes:

• Placing web tier in private subnet
• Assuming load balancer is in private subnet
• Confusing application tier with database tier

4. You deployed a multi-tier app but the application tier in the private subnet cannot connect to the database tier. What is the most likely cause?

medium

A. The load balancer is not configured

B. The web tier is in a public subnet

C. The application tier has a public IP address

D. The database security group does not allow inbound traffic from the application tier

Solution

1. Step 1: Analyze connectivity between application and database tiers

   Application tier must be allowed by database security group to connect on required ports.

2. Step 2: Check common misconfigurations

   If security group blocks inbound traffic, connection fails despite correct subnet placement.

3. Final Answer:

   The database security group does not allow inbound traffic from the application tier -> Option D

4. Quick Check:

   Security group rules control traffic between tiers [OK]

Hint: Check security group rules for inter-tier traffic [OK]

Common Mistakes:

• Blaming web tier subnet for app-db connection
• Assuming public IP needed for private subnet
• Ignoring security group inbound rules

5. You want to design a multi-tier AWS app with a public web tier, private application tier, and private database tier. Which setup best follows best practices?

hard

A. Place all tiers in public subnets with direct internet access for simplicity

B. Place web servers in public subnet with internet gateway; app and database servers in private subnets with NAT gateway for outbound internet

C. Place web and app tiers in private subnets; database in public subnet for easy access

D. Place web tier in private subnet; app and database tiers in public subnets

Solution

1. Step 1: Assign subnet types based on tier roles

   Web tier needs public subnet for user access; app and database tiers should be private for security.

2. Step 2: Provide outbound internet for private tiers

   Use NAT gateway so private tiers can access internet for updates without exposing them inbound.

3. Final Answer:

   Place web servers in public subnet with internet gateway; app and database servers in private subnets with NAT gateway for outbound internet -> Option B

4. Quick Check:

   Public web, private app/db, NAT for outbound [OK]

Hint: Public web, private app/db, NAT gateway outbound [OK]

Common Mistakes:

• Putting database in public subnet
• Giving private tiers direct internet access
• Mixing subnet roles incorrectly