Amazon Machine Learning聽vs聽Elasticsearch

Get Advice Icon

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

Amazon Machine Learning
Amazon Machine Learning

63
83
+ 1
0
Elasticsearch
Elasticsearch

8.9K
5.9K
+ 1
1.6K
Add tool

Amazon Machine Learning vs Elasticsearch: What are the differences?

Developers describe Amazon Machine Learning as "Visualization tools and wizards that guide you through the process of creating ML models w/o having to learn complex ML algorithms & technology". This new AWS service helps you to use all of that data you鈥檝e been collecting to improve the quality of your decisions. You can build and fine-tune predictive models using large amounts of data, and then use Amazon Machine Learning to make predictions (in batch mode or in real-time) at scale. You can benefit from machine learning even if you don鈥檛 have an advanced degree in statistics or the desire to setup, run, and maintain your own processing and storage infrastructure. On the other hand, Elasticsearch is detailed 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).

Amazon Machine Learning belongs to "Machine Learning as a Service" category of the tech stack, while Elasticsearch can be primarily classified under "Search as a Service".

Some of the features offered by Amazon Machine Learning are:

  • Easily Create Machine Learning Models
  • From Models to Predictions in Seconds
  • Scalable, High Performance Prediction Generation Service

On the other hand, Elasticsearch provides the following key features:

  • Distributed and Highly Available Search Engine.
  • Multi Tenant with Multi Types.
  • Various set of APIs including RESTful

Elasticsearch is an open source tool with 41.9K GitHub stars and 14K GitHub forks. Here's a link to Elasticsearch's open source repository on GitHub.

Instacart, Slack, and Stack Exchange are some of the popular companies that use Elasticsearch, whereas Amazon Machine Learning is used by Apli, Cymatic Security, and FetchyFox. Elasticsearch has a broader approval, being mentioned in 1976 company stacks & 936 developers stacks; compared to Amazon Machine Learning, which is listed in 8 company stacks and 9 developer stacks.

- No public GitHub repository available -

What is Amazon Machine Learning?

This new AWS service helps you to use all of that data you鈥檝e been collecting to improve the quality of your decisions. You can build and fine-tune predictive models using large amounts of data, and then use Amazon Machine Learning to make predictions (in batch mode or in real-time) at scale. You can benefit from machine learning even if you don鈥檛 have an advanced degree in statistics or the desire to setup, run, and maintain your own processing and storage infrastructure.

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

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

Why do developers choose Amazon Machine Learning?
Why do developers choose Elasticsearch?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
      Jobs that mention Amazon Machine Learning and Elasticsearch as a desired skillset
      What companies use Amazon Machine Learning?
      What companies use Elasticsearch?

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

      What tools integrate with Amazon Machine Learning?
      What tools integrate with Elasticsearch?
        No integrations found

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

        What are some alternatives to Amazon Machine Learning and Elasticsearch?
        TensorFlow
        TensorFlow is an open source software library for numerical computation using data flow graphs. Nodes in the graph represent mathematical operations, while the graph edges represent the multidimensional data arrays (tensors) communicated between them. The flexible architecture allows you to deploy computation to one or more CPUs or GPUs in a desktop, server, or mobile device with a single API.
        Apache Spark
        Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.
        Amazon SageMaker
        A fully-managed service that enables developers and data scientists to quickly and easily build, train, and deploy machine learning models at any scale.
        RapidMiner
        It is a software platform for data science teams that unites data prep, machine learning, and predictive model deployment.
        Azure Machine Learning
        Azure Machine Learning is a fully-managed cloud service that enables data scientists and developers to efficiently embed predictive analytics into their applications, helping organizations use massive data sets and bring all the benefits of the cloud to machine learning.
        See all alternatives
        Decisions about Amazon Machine Learning and Elasticsearch
        Tim Specht
        Tim Specht
        鈥嶤o-Founder and CTO at Dubsmash | 16 upvotes 54.7K views
        atDubsmashDubsmash
        Memcached
        Memcached
        Algolia
        Algolia
        Elasticsearch
        Elasticsearch
        #SearchAsAService

        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.

        #SearchAsAService

        See more
        Julien DeFrance
        Julien DeFrance
        Full Stack Engineering Manager at ValiMail | 16 upvotes 283.7K 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
        Julien DeFrance
        Julien DeFrance
        Full Stack Engineering Manager at ValiMail | 2 upvotes 12.2K views
        atSmartZipSmartZip
        Amazon SageMaker
        Amazon SageMaker
        Amazon Machine Learning
        Amazon Machine Learning
        AWS Lambda
        AWS Lambda
        Serverless
        Serverless
        #FaaS
        #GCP
        #PaaS

        Which #IaaS / #PaaS to chose? Not all #Cloud providers are created equal. As you start to use one or the other, you'll build around very specific services that don't have their equivalent elsewhere.

        Back in 2014/2015, this decision I made for SmartZip was a no-brainer and #AWS won. AWS has been a leader, and over the years demonstrated their capacity to innovate, and reducing toil. Like no other.

        Year after year, this kept on being confirmed, as they rolled out new (managed) services, got into Serverless with AWS Lambda / FaaS And allowed domains such as #AI / #MachineLearning to be put into the hands of every developers thanks to Amazon Machine Learning or Amazon SageMaker for instance.

        Should you compare with #GCP for instance, it's not quite there yet. Building around these managed services, #AWS allowed me to get my developers on a whole new level. Where they know what's under the hood. Where they know they have these services available and can build around them. Where they care and are responsible for operations and security and deployment of what they've worked on.

        See more
        Interest over time
        Reviews of Amazon Machine Learning and Elasticsearch
        No reviews found
        How developers use Amazon Machine Learning and Elasticsearch
        Avatar of imgur
        imgur uses ElasticsearchElasticsearch

        Elasticsearch is the engine that powers search on the site. From a high level perspective, it鈥檚 a Lucene wrapper that exposes Lucene鈥檚 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.

        Avatar of Instacart
        Instacart uses ElasticsearchElasticsearch

        The very first version of the search was just a Postgres database query. It wasn鈥檛 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鈥檛 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.

        Avatar of AngeloR
        AngeloR uses ElasticsearchElasticsearch

        We use ElasticSearch for

        • Session Logs
        • Analytics
        • Leaderboards

        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.

        Avatar of Brandon Adams
        Brandon Adams uses ElasticsearchElasticsearch

        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.

        Avatar of Ana Phi Sancho
        Ana Phi Sancho uses ElasticsearchElasticsearch

        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.

        Avatar of Taylor Host
        Taylor Host uses Amazon Machine LearningAmazon Machine Learning

        Mild re-training data usage.

        How much does Amazon Machine Learning cost?
        How much does Elasticsearch cost?
        Pricing unavailable
        News about Amazon Machine Learning
        More news