Guide on scaling web app
0 likes99 views
The document discusses the complexities and challenges of scaling web applications, emphasizing the importance of availability, stability, and performance. It outlines various problems such as infrastructure scalability, architecture choices, and security threats, and suggests solutions like CDN caching and microservice architecture. Best practices and tools for measurement and optimization are also highlighted, along with resources for further learning.
Guide on scaling web app
- 2. Ashok Gautam
- 4. Why Anyone can build a whatsapp or facebook copy but scaling it to internet scale is not everyone’s cup of tea. Not even mine Let’s figure out solution together
- 6. Challenges Which will pull us down Availability Stability Bottleneck Latency GEO Disaster Recovery
- 7. Problems to solve 1 Infrastructure Scalability, Uptime, disaster recovery, monitoring 2 Architecture Language, Framework, Database, Storage, Security 3 Cost Compute, Storage, Bandwidth 4 Performance CDN, Rate Limit, API, Caching
- 9. Security HTTPS Access Control Restrict HTTP methods Input validation Validate content types Management endpoints Error handling Audit logs Security headers CORS Sensitive information in HTTP requests ● Parameters Exploitation ● Identity Theft ● Abusing authorization system ● Man-In-The-Middle ● DOS & DDOS ● Cache Poisoning ● Redirection ● XSS ● Injection
- 12. Solution Measure Measure & Measure CDN Caching Multi Level Persistence Multi level DB Application Layer Optimization Micro Service Architecture
- 14. CDN - Not a silver bullet but
- 17. SSD vs HDD
- 19. Reddit ■ 25 servers ■ 2 TB of SQL data all stored on SSDs ■ Each web server has 2x 320GB SSDs in a RAID 1. ■ Each ElasticSearch box has 300 GB also using SSDs. ■ Stack Overflow has a 40:60 read-write ratio. ■ DB servers average 10% CPU utilization ■ 11 web servers, using IIS ■ 2 load balancers, 1 active, using HAProxy ■ 4 active database nodes, using MS SQL ■ 3 application servers implementing the tag engine, anything searching by tag hits ■ 3 machines doing search with ElasticSearch ■ 2 machines for distributed cache and messaging using Redis ■ 2 Networks (each a Nexus 5596 + Fabric Extenders) ■ 2 Cisco 5525-X ASAs (think Firewall) ■ 2 Cisco 3945 Routers ■ 2 read-only SQL Servers for used mainly for the Stack Exchange API
- 20. Tools Measure Measure & Measure AB JMeter XDebug TimeIt Redis Memcache ELK Zabbix Cloud (AWS/GCP) NewRelic Pingdom CloudFlare Cloudinary RDS BigQuery SendGrid
- 21. Best Practices Follow the wisdom ● ● ● ● ● ● ● ● ● ● ●