Amazon Elasticsearch Service聽vs聽Found Elasticsearch

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Amazon Elasticsearch Service
Amazon Elasticsearch Service

202
110
+ 1
19
Found Elasticsearch
Found Elasticsearch

10
8
+ 1
0
Add tool

Amazon Elasticsearch Service vs Found Elasticsearch: What are the differences?

Amazon Elasticsearch Service: Real-time, distributed search and analytics engine that fits nicely into a cloud environment. ; Found Elasticsearch: 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.

Amazon Elasticsearch Service and Found Elasticsearch belong to "Search as a Service" category of the tech stack.

- No public GitHub repository available -
- No public GitHub repository available -

What is Amazon Elasticsearch Service?

Amazon Elasticsearch Service is a fully managed service that makes it easy for you to deploy, secure, and operate Elasticsearch at scale with zero down time.

What is Found 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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Amazon Elasticsearch Service?
Why do developers choose Found Elasticsearch?
    Be the first to leave a pro
      Be the first to leave a con
        Be the first to leave a con
        What companies use Amazon Elasticsearch Service?
        What companies use Found Elasticsearch?

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with Amazon Elasticsearch Service?
        What tools integrate with Found Elasticsearch?
          No integrations found

          Sign up to get full access to all the tool integrationsMake informed product decisions

          What are some alternatives to Amazon Elasticsearch Service and Found Elasticsearch?
          Elasticsearch
          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).
          Amazon CloudSearch
          Amazon CloudSearch enables you to search large collections of data such as web pages, document files, forum posts, or product information. With a few clicks in the AWS Management Console, you can create a search domain, upload the data you want to make searchable to Amazon CloudSearch, and the search service automatically provisions the required technology resources and deploys a highly tuned search index.
          Elastic Cloud
          A growing family of Elastic SaaS offerings that make it easy to deploy, operate, and scale Elastic products and solutions in the cloud. From an easy-to-use hosted and managed Elasticsearch experience to powerful, out-of-the-box search solutions.
          Algolia
          Our mission is to make you a search expert. Push data to our API to make it searchable in real time. Build your dream front end with one of our web or mobile UI libraries. Tune relevance and get analytics right from your dashboard.
          Swiftype
          Swiftype is the easiest way to add great search to your website or mobile application.
          See all alternatives
          Decisions about Amazon Elasticsearch Service and Found Elasticsearch
          Julien DeFrance
          Julien DeFrance
          Full Stack Engineering Manager at ValiMail | 16 upvotes 260.8K views
          atSmartZipSmartZip
          Amazon DynamoDB
          Amazon DynamoDB
          Ruby
          Ruby
          Node.js
          Node.js
          AWS Lambda
          AWS Lambda
          New Relic
          New Relic
          Amazon Elasticsearch Service
          Amazon Elasticsearch Service
          Elasticsearch
          Elasticsearch
          Superset
          Superset
          Amazon Quicksight
          Amazon Quicksight
          Amazon Redshift
          Amazon Redshift
          Zapier
          Zapier
          Segment
          Segment
          Amazon CloudFront
          Amazon CloudFront
          Memcached
          Memcached
          Amazon ElastiCache
          Amazon ElastiCache
          Amazon RDS for Aurora
          Amazon RDS for Aurora
          MySQL
          MySQL
          Amazon RDS
          Amazon RDS
          Amazon S3
          Amazon S3
          Docker
          Docker
          Capistrano
          Capistrano
          AWS Elastic Beanstalk
          AWS Elastic Beanstalk
          Rails API
          Rails API
          Rails
          Rails
          Algolia
          Algolia

          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.

          See more
          Chris McFadden
          Chris McFadden
          VP, Engineering at SparkPost | 8 upvotes 21.9K views
          atSparkPostSparkPost
          Amazon Elasticsearch Service
          Amazon Elasticsearch Service
          Node.js
          Node.js
          Amazon CloudSearch
          Amazon CloudSearch
          Amazon ElastiCache
          Amazon ElastiCache
          Amazon DynamoDB
          Amazon DynamoDB

          We send over 20 billion emails a month on behalf of our customers. As a result, we manage hundreds of millions of "suppression" records that track when an email address is invalid as well as when a user unsubscribes or flags an email as spam. This way we can help ensure our customers are only sending email that their recipients want, which boosts overall delivery rates and engagement. We need to support two primary use cases: (1) fast and reliable real-time lookup against the list when sending email and (2) allow customers to search, edit, and bulk upload/download their list via API and in the UI. A single enterprise customer's list can be well over 100 million. Over the years as the size of this data started small and has grown increasingly we have tried multiple things that didn't scale very well. In the recent past we used Amazon DynamoDB for the system of record as well as a cache in Amazon ElastiCache (Redis) for the fast lookups and Amazon CloudSearch for the search function. This architecture was overly complicated and expensive. We were able to eliminate the use of Redis, replacing it with direct lookups against DynamoDB, fronted with a stripped down Node.js API that performs consistently around 10ms. The new dynamic bursting of DynamoDB has helped ensure reliable and consistent performance for real-time lookups. We also moved off the clunky and expensive CloudSearch to Amazon Elasticsearch Service for the search functionality. Beyond the high price tag for CloudSearch it also had severe limits streaming updates from DynamoDB, which forced us to batch them - adding extra complexity and CX challenges. We love the fact that DynamoDB can stream directly to ElasticSearch and believe using these two technologies together will handle our scaling needs in an economical way for the foreseeable future.

          See more
          Interest over time
          Reviews of Amazon Elasticsearch Service and Found Elasticsearch
          Review ofFound ElasticsearchFound Elasticsearch

          We use found.no to host our elasticsearch index for ninya.io[1].

          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[2]. I'd also like to recommend their blog[3] that is full of technical articles not necessarily scoped to their service but also elasticsearch in general.

          How developers use Amazon Elasticsearch Service and Found Elasticsearch
          Avatar of Charles LaPress
          Charles LaPress uses Amazon Elasticsearch ServiceAmazon Elasticsearch Service

          By streaming data from Dynamodb Elasticsearch provides the dynamic lookups for listings by activity, date, cost, ect. ect, providing a superior enduser experience.

          How much does Amazon Elasticsearch Service cost?
          How much does Found Elasticsearch cost?
          Pricing unavailable
          News about Found Elasticsearch
          More news