lifecycle-of-web-app.md

lifecycle-of-web-app.md

Lifecycle of a web-app

Browser-side and Server-side

Client makes a request from the browser which then goes to the server to fetch some resources. The server is a really complex thing that does all the logic handling, computations and provides us with the things that we eventually want to show on the website. That covers authorization, authentication and interaction with the database. Authentication

• Authentication is the process of verifying who you are. When you log on to a PC with a user name and password you are authenticating.

• Authorization is the process of verifying that you have access to something. Gaining access to a resource (e.g. directory on a hard disk) because the permissions configured on it allow you access is authorization.

Scalability and Perfomance

• Microservices
  1. https://opensource.com/resources/what-are-microservices
  2. API gateway: Because there would be a lot of containers / services, it would be hard for the client - side browser to check which request should be served by which container / service. So, for that task we build API gateway. The browser just requests an API to the API gateway and then it is the responsibility of the API gateway to find which service is responsible for this request.
• Caching with Redis:
  1. https://codeburst.io/redis-what-and-why-d52b6829813
  2. https://www.codementor.io/brainyfarm/introduction-to-caching-and-redis-h6o16p4qx