Reliability

The previous chapters have described the underlying technologies such as consistent hashing, ID generator, and now using these techniques we can develop a URL shortener that can generate 100 million URLs per day.

Design consists of the following elements:

• API endpoints
• URL redirecting
• URL shortening
• Data model
• Hash functions: Hash + collision resolution vs Base-62 conversion
• Additional topics to consider:
  • Rate limiter
  • Web server scaling
  • Database scaling
  • Analytics
  • Availability, consistency, and reliability

These items are disclosed in a very interesting Chapter 8 of the book:

Earlier this year the book club of our company has studied excellent book:

Martin Kleppmann - Designing Data-Intensive Applications

This is the best book I have read about building complex scalable software systems. 💪

As usually (to better learn) I prepared an overview and mind-map.

Chapter 1:

• Building blocks of the apps
• What is Reliability, Scalability and Maintainability. Examples and definitions.
  • Faults and Failures
  • Performance, Load, Latency and Response Time
  • Operability, Simplicity, Evolvability
• Why you should randomly kill your servers 😅
• How Twitter delivers 12,000 tweets per second to 300,000 readers per second. (VERY interesting!)
• How much money Amazon loses for each 100ms delay in their response time
• How to quickly calculate percentiles for monitoring response time in PROD

Download full mind map (PDF)