WhatsApp System Design - Step by Step

Рет қаралды 1,604

Жыл бұрын

This is a step by step tutorial on System Design of a Messaging Chat application, WhatsApp in this example
Full tutorial here - kindsonthegenius.com/system-d...
Six steps
1. Functional Requirements
2. Non-Functional Requirements
3. System Design Components
4. Message Storage Choice
5. Message Processing and Routing
6. Implementing Selected Requirements
System Design for TikTok here - • TikTok System Design -...
www.kindsonthegenius.com
www.datarmatics.com
www.munonye.com
Learn Programming by joining International Computer Programmers Group:
👉 / internationalcomputerp...
You can reach me via any of the following
❤️ Instagram: / kindsonthegius
❤️ LinkedIn: / kindson
❤️ Pinerest: / kindsonm
❤️ Facebook: / kindsonm
❤️ Tumblr: www.tumblr.com/blog/kindsonth...
❤️ Twitter: / kindsonm
Your support can help me improve my content:
✅ Buy me a coffee: www.buymeacoffee.com/KindsonM
✅ Support me on Patreon: / kindsonthegenius
The Piano Man kindsonthepianoman.blogspot.com/

Пікірлер: 5

@Submarin7 Жыл бұрын

Thank you 😊

@yogeez123 Жыл бұрын

As I reach to Session Manager - it is not clear. What is session manager ? Session Manager is a very generic and vague term and how sessionId works in distributed env unless it is a sticky session ? what is pid in lookup table ? If we are in distributed env with more than one messaging server then how does this work as we will have multiple session managers ? Also the two important things : concurrency and protocol are not discussed. It seems like that lookup table needs to be cached inside each messaging server. For e.g. if A is connected to messaging server 1 and wants to send message to B which is connected to server 2 then how does it work unless lookup table is cached inside each messaging server ? And another big thing is - how do you keep all the cached table in sync ?

@uyuo2 Жыл бұрын

How do you prevent out of sequence delivery?

@KindsonTheTechPro Жыл бұрын

That's a good question. There are two ways: (1) a message queue or buffer is maintained in the client side that implements a FIFO strategy (2) this involved use of message correlation id but it's a bit more involved