Capacity Estimation for UPI System Design
Below is the capacity estimation for UPI system design:
- Traffic Estimate
- Users: 100 million users
- Daily Active Users (DAU): 10 million users
- Transactions per User per Day: 5 transactions
- Total Transactions per Day: 50 million transactions
- Storage Estimate
- Average Transaction Size: 500 bytes
- Daily Data: 50 million * 500 bytes = 25 GB
- Monthly Data: 25 GB * 30 = 750 GB
- Yearly Data: 750 GB * 12 = 9 TB
- Bandwidth Estimate
- Request Size: 1 KB
- Response Size: 1 KB
- Total Requests per Day: 50 million
- Total Data per Day: (50 million * 2 KB) / (1024 * 1024) = ~95 GB
- Memory Estimate
- Active Users Cached: 1 million
- Data per User: 1 KB
- Total Memory: 1 million * 1 KB = 1 GB
Designing UPI – System Design
Designing a Unified Payments Interface (UPI) system involves creating an architecture that enables real-time inter-bank transactions through a seamless and secure platform. Key components include user interfaces, a central UPI switch managed by the National Payments Corporation of India (NPCI), backend systems of participating banks, and third-party service providers.
- The system supports core functionalities such as user registration and authentication, payment initiation and authorization, inter-bank transaction processing, and real-time settlement.
- Security measures like encryption and multi-factor authentication ensure compliance and protect against fraud, making UPI a reliable and efficient payment solution.
- The UPI is a real-time payment system that facilitates inter-bank transactions by instantly transferring funds between two bank accounts on a mobile platform.
Important Topics for UPI system design
- Functional Requirements for UPI System Design
- Non-Functional Requirements for UPI System Design
- Capacity Estimation for UPI System Design
- High-Level Design(HLD) for UPI System Design
- Low-Level Diagram(LLD) for UPI System Design
- Microservices Used in UPI System Design
- Scalability for UPI System Design