Elasticsearch vs Found Elasticsearch: What are the differences?
Developers describe Elasticsearch as "Open Source, Distributed, RESTful Search Engine". Elasticsearch is a distributed, RESTful search and analytics engine capable of storing data and searching it in near real time. Elasticsearch, Kibana, Beats and Logstash are the Elastic Stack (sometimes called the ELK Stack). On the other hand, Found Elasticsearch is detailed as "Hosted Elasticsearch". Create your own fully managed and hosted Elasticsearch cluster. You get a dedicated cluster with reserved memory, giving you predictable performance. There are no arbitrary limits on how many indexes or documents you can store. Scale your clusters as and when needed, without any downtime.
Elasticsearch and Found Elasticsearch belong to "Search as a Service" category of the tech stack.
Some of the features offered by Elasticsearch are:
- Distributed and Highly Available Search Engine.
- Multi Tenant with Multi Types.
- Various set of APIs including RESTful
On the other hand, Found Elasticsearch provides the following key features:
- Hosted and managed: You get your own fully hosted and managed Elasticsearch cluster. No need to host and maintain your own costly search infrastructure.
- Reserved Memory and storage: Your clusters get reserved memory and storage. No shared clusters and no arbitrary limits on how many indexes or documents you can store.
- Scalable and flexible: Start small, grow big. You can scale your cluster as and when needed, without any downtime. There are several Elasticsearch versions to choose from, and upgrading is easier than ever.
Elasticsearch is an open source tool with 42.4K GitHub stars and 14.2K GitHub forks. Here's a link to Elasticsearch's open source repository on GitHub.
What is Elasticsearch?
What is Found Elasticsearch?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Found Elasticsearch?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Found Elasticsearch?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Found Elasticsearch?
Sign up to get full access to all the tool integrationsMake informed product decisions
Although we were using Elasticsearch in the beginning to power our in-app search, we moved this part of our processing over to Algolia a couple of months ago; this has proven to be a fantastic choice, letting us build search-related features with more confidence and speed.
Elasticsearch is only used for searching in internal tooling nowadays; hosting and running it reliably has been a task that took up too much time for us in the past and fine-tuning the results to reach a great user-experience was also never an easy task for us. With Algolia we can flexibly change ranking methods on the fly and can instead focus our time on fine-tuning the experience within our app.
Memcached is used in front of most of the API endpoints to cache responses in order to speed up response times and reduce server-costs on our side.
Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.
I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.
For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.
Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.
Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.
Future improvements / technology decisions included:
Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic
As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.
One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.
We use found.no to host our elasticsearch index for ninya.io.
When we were looking for an elasticsearch provider we compared a couple of different services. One thing that we considered as a big advantage over other elasticsearch provider is the simple pricing. Most other elasticsearch provider use document limits whereas found.no uses storage quota which makes more sense to us.
found.no supports all elasticsearch features and has been very reliable for us. They also have an amazing customer support that helped us to resole issues (on our end) quickly when we didn't know how to help ourselves.
Getting started with found.no was a piece of cake. There's everything you need right at your dashboard. They even generate examples for exactly your account which is really helpful to get newcomers started.
For everything else there is great documentation right on there website. I'd also like to recommend their blog that is full of technical articles not necessarily scoped to their service but also elasticsearch in general.
Elasticsearch is the engine that powers search on the site. From a high level perspective, it’s a Lucene wrapper that exposes Lucene’s features via a RESTful API. It handles the distribution of data and simplifies scaling, among other things.
Given that we are on AWS, we use an AWS cloud plugin for Elasticsearch that makes it easy to work in the cloud. It allows us to add nodes without much hassle. It will take care of figuring out if a new node has joined the cluster, and, if so, Elasticsearch will proceed to move data to that new node. It works the same way when a node goes down. It will remove that node based on the AWS cluster configuration.
The very first version of the search was just a Postgres database query. It wasn’t terribly efficient, and then at some point, we moved over to ElasticSearch, and then since then, Andrew just did a lot of work with it, so ElasticSearch is amazing, but out of the box, it doesn’t come configured with all the nice things that are there, but you spend a lot of time figuring out how to put it all together to add stemming, auto suggestions, all kinds of different things, like even spelling adjustments and tomato/tomatoes, that would return different results, so Andrew did a ton of work to make it really, really nice and build a very simple Ruby gem called SearchKick.
We use ElasticSearch for
- Session Logs
We originally self managed the ElasticSearch clusters, but due to our small ops team size we opt to move things to managed AWS services where possible.
The managed servers, however, do not allow us to manage our own backups and a restore actually requires us to open a support ticket with them. We ended up setting up our own nightly backup since we do per day indexes for the logs/analytics.
Elasticsearch has good tooling and supports a large api that makes it ideal for denormalizing data. It has a simple to use aggregations api that tends to encompass most of what I need a BI tool to do, especially in the early going (when paired with Kibana). It's also handy when you just want to search some text.
Self taught : acquired knowledge or skill on one's own initiative. Open Source Search & Analytics. -time search and analytics engine. Search engine based on Lucene. It provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents.