System Overview - Relational database strengths
This system uses a relational database to store and manage structured data with clear relationships. It supports complex queries, ensures data accuracy, and maintains consistency through transactions.
0
0
Relational database strengths in HLD - Architecture Diagram
Architecture Diagram
User | v Load Balancer | v API Gateway | v Application Service | v Cache | v Relational Database
Components
User
client
Initiates requests to the system
Load Balancer
load_balancer
Distributes incoming requests evenly to prevent overload
API Gateway
api_gateway
Handles request routing, authentication, and rate limiting
Application Service
service
Processes business logic and interacts with the database
Cache
cache
Stores frequently accessed data to reduce database load and improve response time
Relational Database
database
Stores structured data with relationships, supports ACID transactions
Request Flow - 11 Hops
User → Load Balancer
Load Balancer → API Gateway
API Gateway → Application Service
Application Service → Cache
Cache → Application Service
Application Service → Relational Database
Relational Database → Application Service
Application Service → Cache
Application Service → API Gateway
API Gateway → Load Balancer
Load Balancer → User
Failure Scenario
Component Fails:Relational Database
Impact:Data writes fail and fresh data cannot be retrieved; cached reads may still work but data may be stale
Mitigation:Use database replication for failover; serve reads from cache during outage; queue writes for retry after recovery
Architecture Quiz - 3 Questions
Test your understanding
Which component ensures that user requests are evenly distributed to prevent overload?
Design Principle
This architecture highlights the strength of relational databases in managing structured data with clear relationships and ensuring data consistency through ACID transactions. The use of caching improves performance by reducing database load for frequent reads.