This was very in-depth and informative, Leonardo. Loved the diagrams as well as usual.
My only feedback would be that it may be nice to split an article like this into 2 parts, since there is a lot of ground to cover in one, and I think I'd remember it easier. Still, it's apparent you put a lot of time and effort into this to be exhaustive and give really in-depth takeaways which I love
Thank you Jordan! You're very right - this one was much longer than I expected. Definitely will have to limit the length or split them in the future. Appreciate it!
The diagram showed in "Reducing Latency" section is incorrect wrt to mcrouter placement. Facebook used mcrouter as both client (installed on the web server instance itself) and server side proxy (separate proxy server instance used to route the invalidation batch messages from mcsqueal)
This was very in-depth and informative, Leonardo. Loved the diagrams as well as usual.
My only feedback would be that it may be nice to split an article like this into 2 parts, since there is a lot of ground to cover in one, and I think I'd remember it easier. Still, it's apparent you put a lot of time and effort into this to be exhaustive and give really in-depth takeaways which I love
Thank you Jordan! You're very right - this one was much longer than I expected. Definitely will have to limit the length or split them in the future. Appreciate it!
The diagram showed in "Reducing Latency" section is incorrect wrt to mcrouter placement. Facebook used mcrouter as both client (installed on the web server instance itself) and server side proxy (separate proxy server instance used to route the invalidation batch messages from mcsqueal)