Operations | Monitoring | ITSM | DevOps | Cloud

There are many ways to add search functionality to a Rails application. While many Rails developers choose to use the native search functionality built into popular databases like MySQL and Postgres, others need more flexible or feature rich search functionality. ElasticSearch is probably the most well known option available but it has its own issues. Firstly, it is a resource hungry beast. To run ElasticSearch properly in production, you need a few beefy servers.

At ElasticON Global 2021, we shared a future view of Elastic Enterprise Search and how we’re continuing to build next-generation, machine learning-powered search experiences backed by the speed, scale, and relevance of Elasticsearch. We also highlighted the many ways we plan to keep building even more flexibility into our solutions.

We are pleased to announce the general availability of Elastic 7.15, a release that brings a broad set of new capabilities to the Elastic Search Platform (including Elasticsearch and Kibana) and its three built-in solutions — Elastic Enterprise Search, Elastic Observability, and Elastic Security.

Our first tutorial gave a general introduction to OpenSearch installation and configuration. We recently also published a comparative introduction for OpenSearch queries (and how they parallel or contrast with Elasticsearch). Now, we’ll continue that series with an intro to OpenSearch clusters. This is a very simple tutorial with straight-forward examples, but we will try to cover some detail and common advanced settings.

OpenSearch has evolved rapidly since its fork from the source code of the last truly open source version of Elasticsearch. So far, the community’s work has focused on removing proprietary code from Elastic, including a number of things that were never purely open source themselves. These include some aspects of the querying languages and capabilities of Elasticsearch.

Security is a top-of-mind topic for software companies, especially those that have experienced security breaches. Companies must secure data to avoid nefarious attacks and meet standards such as HIPAA and GDPR. Audit logs record the actions of all agents against your Elasticsearch resources. Companies can use audit logs to track activity throughout their platform to ensure usage is valid and log when events are blocked.