Usually Sound choices
- Scaling
- Load balancing and solve the session problem (likely with a persistent cache)
- Caching with a memory based cache
Database decisions
- Relational Database vs. NoSQL
Other ideas
- Asynchronous server side pre-rendering of rarely changing pages
Scalability vs. Performance
If a service is slow for a single user you have a performance problem, if it is fast for a single user but slow under load you have a scaling problem.
Latency vs. throughput
Latency is the time to perform some action or to produce
Replication and Fail-over
Replication is the maintenance of copies of state (typically database state in systems, but application images is another example). Fail-over is the promotion of a system to serve requests.
Engineering Blogs
Engineering at Meta Google Research Google Cloud Blog AWS Architecture Blog All Things Distributed The Nextflix Tech Blog LinkedIn Engineering Blog Uber Engineering Blog Engineering at Quora Pinterest Engineering Lyft Engineering Blog Twitter Engineering Blog Dropbox Engineering Blog Spotify Engineering Github Engineering Instagram Engineering Databricks Canva Engineering Blog Etsy Engineering Booking.com Tech Blog Expedia Technology The Airbnb Tech Blog Stripe Engineering Blog Ebay Tech Blog Flickr’s Tech Blog Hubspot Product and Engineering Blog Zynga Engineering Yelp Engineering Blog Heroku Engineering Blog Discord Engineering and Design Zomato Hotstar Swiggy Acast Tech ASOS Tech Blog Shopify Engineering Microsoft Tech Blogs Engineering at Microsoft MongoDB Engineering Blog Slack Engineering Engineering at Depop SourceDiving (Cookpad’s Engineering Blog Auto Trader Engineering Blog Indeed Engineering Blog Gusto Engineering Blog Engineering at Birdie Forethough Engineering Capital One Disney Streaming