Skip to content

chipbk10/SystemDesign

Repository files navigation

System Design

  1. How does https work? https, handshake
  2. Where is a shared session key stored? https
  3. How to avoid handshake overhead for subsequent https requests? keep-alive
  4. How to resume previous https session without doing a full handshake? partial handshake
  5. How to route the subsequent https request to the same server? sticky session
  6. How does login work? session_token, access_token, jwt, authenticate, password

Handle Failures

  1. How would you design your API to handle unreliable downstream services and ensure it remains responsive and reliable for users? circuit breaker, resilience
  2. You’re tasked with designing a microservices-based web application with multiple services that need to communicate with each other. These services are deployed on Kubernetes, and you need to ensure reliable communication, handle failures gracefully, enforce rate limits between services, and monitor traffic without adding significant complexity to the application code. How would you approach this problem, and what tools or strategies would you use to achieve these goals? service mesh, circuit breaker, rate limiting, resilience

Security

  1. How to ensure that a message received over https is not altered and comes from a trusted source? signature, certificate
  2. How does ssl-pinning enhance mobile app security? ssl-pinning
  3. Why isn't ssl-pinning used in web app? ssl-pinning

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages