Building software
sari and
Building software
System Design Interview – An Insider's Guide: Volume 2
amazon.com
Inverse-Conway-Maneuver: How to speed up product development teams successfully
Tobias Soffnerthoughtworks.com
The Pulse #92: GitHub’s AI-assisted developer workflow vision
Gergely Orosznewsletter.pragmaticengineer.com
Pros
- The query speeds improve as, instead of instructing Elasticsearch to Get all the data matching... , you say Go there and get all the data matching... ( Fig 6 ). If you are querying data with multiple unique routing keys, this guarantees better or equivalent query performance as that of the default routing strategy (reducing the scatter and
Improving query performance in ElasticSearch at scale
The formula in Fig 5 is one of the reasons why Elasticsearch does not allow the update of the number of primary shards post index creation. What the default routing guarantees is that the data will be uniformly distributed across the cluster which would reduce query hotspots when retrieving documents