GFG High Level Design

• High_Level_Design

• 

• Cap theorem- Choose only 2/3

• 

• 

• In last classmaster_slave database was discussed,

• In last classmaster_slave database was discussed.

• CAConsistency andAvailability comes from SQL Database

• 

• So selecting Database should be done based on these three things.

• Partition_Tolerance is about having seperation between nodes so that nodes that fail don’t affect the other nodes.

• InBFSI domainAtomicity is important, transactions are important since everything should happen or rollback elegantly.

• base_theorem

• Caching

• 

• In below diagram, the caching server can be replaced with cache layer which will basically be a method or interceptor for the API calls or a method deciding to pick data from state or localstorage based on if parsed data is present there,

• proxy_server

• 

• forward_proxy andreverse_proxy

• forward_proxy is used by education institutes to block request to certain website like facebook.

• Content Delivery Network,

• HTTP

Queuing

• 
• Celery is good for queue, can be used with Redis or RabbitMQ

AWS- Amazon Web Services S3

• 

Elastic Search

• Search ELK, you will get good kabana searchboards.
• 

kafka

• 

AWS- Amazon Web Services lambda

Previous class PDF

Questions

• Q. Will this PDF be shared?
• Q. How does the pricing of cloud providers get affected by Websockets & socket.io vsHTTP ?
• Q. Do all serverless functions work as observers?
• Q.