How akhileshthykkat/url-shortener works
Main Components
A. Client Layer
• Web Browsers/API Clients
• Interaction with the API endpoints
B. Application Layer (Node.js + Express)
• Authentication Service
• URL Shortening Service
• Analytics Service
• Rate Limiting Middleware
C. Caching Layer
• Redis Cache (Upstash)
• Caching of frequently accessed URLs
D. Database Layer
• PostgreSQL Database (Neon)
• Different data models (URLs, Users, Analytics)
Component Relationships
[Client Layer]
• ↓ ↑
[Load Balancer/API Gateway]
• ↓ ↑
[Application Layer]
• ↓
• [Rate Limiter]
• ↓
• [Auth Middleware]
• ↓
[Services Layer]
• ↓ ↓ ↓
[URL] [User] [Analytics]
• /
• /
• ↓ ↓ ↓
[Redis Cache]
• ↓ ↑
[PostgreSQL]
Detailed Component Breakdown
A. API Layer (from src/routers):
• auth.js → Authentication routes
• shorten.js → URL shortening routes
• analytics.js → Analytics routes
B. Services Layer (from src/services):
• url.js → URL management
• user.js → User management
• clickEvent.js → Click tracking
• dailyStat.js → Daily statistics
• deviceStat.js → Device analytics
• osStat.js → Operating system analytics
C. Data Models (from src/models):
• URL
• User
• ClickEvent
• DailyStat
• DeviceStat
• OsStat
Additional Elements
A. Security Components:
• Google OAuth2 integration
• JWT token validation
• Rate limiting
B. Infrastructure Components:
• Docker container
• Render.com hosting
• Upstash Redis
• Neon PostgreSQL
The scalability points (where load balancing can be implemented)
This will provide a clear understanding of both the current architecture and potential scaling points for future growth.