Building software
sari and
Building software
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
amazon.comPros
- 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
System Design Interview – An Insider's Guide: Volume 2
amazon.com
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
Inverse-Conway-Maneuver: How to speed up product development teams successfully
Tobias Soffnerthoughtworks.com
The "Painless" data migration
- Another challenge was to incorporate the above changes for the existing data i.e. increasing the number of shards and defining a custom routing key for each of the document. The existing index had close to 33 MN documents at the time of the change
- Given that the routing key and the number of shards needed to changes, a