If I had to scale a system, I'd try these techniques:
1 Horizontal Scaling
2 Autoscale
3 Retries
4 Orchestration
5 High Availability
6 Lazy Load
7 gRPC
8 Data Archiving
9 Backend for Frontend
10 Priority Queues
11 Edge Computing
12 Delta Sync
13 Brownout Mode
14 Kernel Bypass
15 Vertical Scaling
16 Microservices
17 Rate Limit
18 Service Mesh
19 Graceful Degradation
20 Capacity Planning
21 Pagination
22 Tiered Storage
23 Request Coalescing
24 Dead Letter Queues
25 Edge Authentication
26 Change Data Capture
27 Leaky Bucket Smoothing
28 Async Non-Blocking IO
29 Caching
30 Event Driven
31 Circuit Breaker
32 Diagonal Scale
33 Consistent Hashing
34 Hot Standby
35 Database Connection Pooling
36 TTL Expiration
37 Batch Reads
38 Stream Processing
39 Static Site Generation
40 Storage Partition Pruning
41 Token Bucket Throttling
42 Thread Pool Tuning
43 Load Balance
44 Queueing
45 Backpressure
46 CDN
47 CAP Tradeoff
48 Read Replica
49 Materialized Views
50 Log Compaction
51 Idempotency Keys
52 Micro-Batching
53 Incremental Static Regeneration
54 Client-Side Caching
55 Adaptive Timeouts
56 Load Shedding
57 Sharding
58 Stateless
59 GeoDNS
60 Monitoring
61 Modularity
62 Write Batching
63 Query Result Caching
64 Event Sourcing
65 Asynchronous Workflows
66 Data Locality
67 Server-Side Rendering Cache
68 Columnar Storage for Analytics
69 In-Memory Data Grids
70 Admission Control
71 Replication
72 Indexing
73 Multi Region
74 Tracing
75 Bulkhead
76 Compression
77 Denormalization
78 CQRS
79 Job Scheduling
80 Regional Read Caches
81 Edge Image Transformation
82 Search Offloading
83 Memory-Mapped Files
84 Concurrency Limits
85 Partition
86 Timeouts
87 Container
88 Failover
89 Prefetching
90 HTTP Keep-Alive
91 Read/Write Splitting
92 API Gateway
93 Worker Pools
94 Anycast Routing
95 Optimistic UI with Deferred Sync
96 Specialized Datastores
97 Zero-Copy Networking
98 Hedged Requests
(...and much more.)
What else should make this list?
===
💾 Save this for later & restack it to help others learn system design.