Guide to running Elasticsearch in production (facinating.tech)

Article summary

The article provides a guide to running Elasticsearch in production, but its contents are not directly available. The discussion revolves around the challenges and considerations of deploying Elasticsearch, including security, scalability, and reliability. Commenters share their experiences and opinions on the best practices for running Elasticsearch in production. Security is a major concern, with some commenters emphasizing the importance of proper configuration and others discussing the limitations of Elasticsearch's security features.

Main themes

• Elasticsearch security
• Production deployment
• Scalability and reliability
• Configuration best practices
• Alternative solutions
• Data loss and inconsistencies
• Documentation and support
• Subscription tiers and pricing

What commenters say

• Elasticsearch's security features are limited and require careful configuration to prevent breaches.
• The default settings of Elasticsearch can lead to security vulnerabilities if not properly configured.
• Some commenters have had positive experiences with Elasticsearch's scalability and reliability, while others have faced challenges.
• The use of a reverse proxy server or a paid Elastic cluster can improve security, but may not be necessary for all use cases.
• Elasticsearch is not suitable as a primary database due to its potential for data loss and inconsistencies.
• The documentation for Elasticsearch's security features can be confusing and outdated, leading to misunderstandings about its capabilities.
• Alternative solutions, such as OpenDistro for Elasticsearch, may offer better security features and support.
• Proper security configuration is crucial to prevent breaches, and commenters recommend prioritizing security when deploying Elasticsearch in production.
• The complexity of Elasticsearch's subscription tiers and security features can make it difficult to understand and configure properly.