You write "The communication paths between engineers increase exponentially as the team grows in size.", but in fact the total number of communication paths between n nodes is equal to n * (n-1) / 2, which is not an exponential growth, but an polynomial growth (quadratic to be exact), i.e. O(n^2).
You have given a good overview on the type of technology stack used, it would have been much more helpful if you could have included about databases, and messaging queue being used.
I appreciate it. Your points that you've touched on in this post are crucial: communication paths, small team size etc. The great article and references.
Hi,
You write "The communication paths between engineers increase exponentially as the team grows in size.", but in fact the total number of communication paths between n nodes is equal to n * (n-1) / 2, which is not an exponential growth, but an polynomial growth (quadratic to be exact), i.e. O(n^2).
thanks for the great feedback. I will update the post.
Great read
Nothing escapes the Math Police 🙌🏿
Excellent explanation.
Great read, Neo! In short don’t reinvent the wheel and avoid complexity as long as possible.
I bet Jan Koum is glad he got rejected by Facebook in 2008! Thanks for the article.
yeah the moral of the story is life gifts are not obvious because they are wrapped in rejection letters.
I learned so much reading this. Also thank you for the bibliography/works cited.
While diagonal Scaling is an interesting infrastructure scaling, the use of load testing and the small team size were eye-opening
This allows me to delve deeper into some of mentioned concepts
thanks for the feedback
Great post! As someone who is building his own product, articles like these are a treat.
Hi,
Thanks for the wonderful newsletter.
You have given a good overview on the type of technology stack used, it would have been much more helpful if you could have included about databases, and messaging queue being used.
thanks for the feedback.
Patterns
this is a good resource. thanks for posting this @Neo
I would have loved more if you included some points around: technical choices(what/why/how) trade offs | implementation details of some example(code)
What other systems use what whatsapp use? Why is it so?
If we have to design it from scratch with today's tech stack, what would be a good choice?
Thanks for sharing !
You don’t need special things to do good. You need the right things
I appreciate it. Your points that you've touched on in this post are crucial: communication paths, small team size etc. The great article and references.
A great article, which does not explain why they were able to support 50 billion messages.
Thanks a lot! Super interesting.
Thanks for explaining it with clarity while being concise.
A quick question, what software are you using for your diagrams? I like their sketch feel.
it's excalidraw.