How nomoreft/private-isu works
Main System Components
a. Web Application Layer
• Multiple language implementations (Ruby, Go, PHP, Node.js)
• Uses Nginx as reverse proxy
• Implements a social media-like application with posts and user management
• Uses templates for view rendering
b. Database Layer
• MySQL for persistent storage
• Memcached for caching
c. Benchmarker Component
• Standalone Go application
• Contains user data for testing
• Implements scoring system
• Includes checker and scenario modules
d. Portal Component (Legacy)
• Ruby on Rails application
• Manages teams, users, and jobs
• Uses Sidekiq for background processing
• Includes scoring dashboard
[Client Browsers]
• ↓
[Load Balancer/Nginx]
• ↓
[Web Application Layer]
• Ruby App (default)
• Go App
• PHP-FPM App
• Node.js App
• ↓
[Data Layer]
• MySQL
• Memcached
[Benchmarker Component] ←→ [Target Application]
• Scenario Runner
• Score Calculator
• User Data Store
[Portal Component]
• Web Interface
• Sidekiq Workers
• Redis
Connection Types
• Double lines: Data replication/sync
Important Elements to Highlight
a. Infrastructure:
• Separation between competitor instances and benchmarker instances
• AWS deployment options
• Available deployment methods (Docker, Vagrant, bare metal)
b. Application Flow:
• Request handling path
• Data access patterns
• Caching strategy
• Benchmark execution flow
Additional Details
Annotations for:
• Port numbers (80, 3000, etc.)
• Language-specific components
• Configuration file locations
• Resource limits and constraints
Performance-Critical Paths
• Main request processing path
• Database query routes
• Cache access patterns
• Benchmark measurement points
Deployment Options
• AMI deployment
• Docker Compose setup
• Vagrant configuration
• Manual installation
This system design should help the principal software engineer understand both the overall architecture and the specific components that are likely to be performance bottlenecks during the ISUCON competition.