elasticsearch-best-practices

- Design indices and mappings based on query patterns - Optimize for search performance with proper analysis and indexing - Use appropriate shard sizing and cluster configuration - Implement proper security and access control - Monitor cluster health and optimize queries - Define explicit mappings instead of relying on dynamic mapping - Use appropriate data types for each field - Disable indexing for fields you do not search on - Use keyword type for exact matches, text for full-text search - keyword : Exact values, filtering, aggregations, sorting - text : Full-text search with analysis - date : Date/time values with format specification - numeric types : long, integer, short, byte, double, float, scaled_float - boolean : True/false values - geo_point : Latitude/longitude pairs - nested : Arrays of objects that need independent querying - Target 20-40GB per shard - Aim for ~20 shards per GB of heap - Avoid oversharding (too many small shards) - Consider time-based indices for time-series data - Use filter context for non-scoring queries (cacheable) - Use must only when scoring is needed - Avoid wildcards at the beginning of terms - Use keyword fields for exact matches - Limit result size with size parameter - Use size: 0 when you only need aggregations - Set appropriate shard_size for terms aggregations - Use composite aggregations for pagination - Consider using aggs filters...