Distributed in-process cache can make things very fast. See vimeo with group cache: https://medium.com/vimeo-engineering-blog/video-metadata-caching-at-vimeo-a5

Distributed in-process cache can make things very fast. See vimeo with group cache: https://medium.com/vimeo-engineering-blog/video-metadata-caching-at-vimeo-a54b25f0b304 https://medium.com/vimeo-engineering-blog/video-metadata-cac... Or in-process distributed rate limiting: https://github.com/mailgun/gubernator https://github.com/mailgun/gubernator https://github.com/golang/groupcache https://github.com/golang/groupcache: groupcache is in production use by dl.google.com (its original user), parts of Blogger, parts of Google Code, parts of Google Fiber, parts of Google production monitoring systems, etc. There was also a paper by google that I can't find right now. Edit: Found it https://blog.acolyer.org/2019/06/24/fast-key-value-stores/ https://blog.acolyer.org/2019/06/24/fast-key-value-stores/