HomeCourseBackend High Lavel Design

Backend High Lavel Design

Backend High Lavel Design

Categories: HLD
Wishlist Share
Share Course
Page Link
Share On Social Media

About Course

Load Balancing

  • Minimum Viable Product (MVP)
  • Module Introduction
  • Why do we need distributed system
  • What happens to the user’s data when a user does not logout ?
  • DNS and ICANN
  • how a URL is different from the IP address or how they are related?
  • What is reason of keeping layered design.
  • Do root DNS sync up with ICANN servers often
  • How can people globally and uniquely identify a domain name
  • Will it take longer for you to connect to Google DNS because you are overwriting the default DNS?
  • Distribution of load
  • Is IP assigned by ISP , get added in ICANN Domain
  • So if we consider the cost, we are getting better configuration in horizontal…. Then where we should use vertical

Caching

  • Separating Application & Database
  • Caching
  • Caching Layers for Backend Infrastructure
  • Content Delivery Network (CDN)
  • What is Anycast and Why Anycast
  • Backend Caching
  • – Local Caching vs Global Caching 
  • – Single vs. Distributed Cache
  • Issues with Cache
  • Eviction Policies
  • Immediate Consistency / Strong Consistency
  • Eventual Consistency
Show More