Apigee vs Divshot vs Elasticsearch

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

Apigee

176
482
+ 1
26
Divshot

15
28
+ 1
42
Elasticsearch

23.9K
17.8K
+ 1
1.6K
Advice on Apigee, Divshot, and Elasticsearch
André Ribeiro
at Federal University of Rio de Janeiro · | 4 upvotes · 12.6K views

Hi, community, I'm planning to build a web service that will perform a text search in a data set off less than 3k well-structured JSON objects containing config data. I'm expecting no more than 20 MB of data. The general traits I need for this search are: - Typo tolerant (fuzzy query), so it has to match the entries even though the query does not match 100% with a word on that JSON - Allow a strict match mode - Perform the search through all the JSON values (it can reach 6 nesting levels) - Ignore all Keys of the JSON; I'm interested only in the values.

The only thing I'm researching at the moment is Elasticsearch, and since the rest of the stack is on AWS the Amazon ElasticSearch is my favorite candidate so far. Although, the only knowledge I have on it was fetched from some articles and Q&A that I read here and there. Is ElasticSearch a good path for this project? I'm also considering Amazon DynamoDB (which I also don't know of), but it does not look to cover the requirements of fuzzy-search and ignore the JSON properties. Thank you in advance for your precious advice!

See more
Replies (3)
Ted Elliott

I think elasticsearch should be a great fit for that use case. Using the AWS version will make your life easier. With such a small dataset you may also be able to use an in process library for searching and possibly remove the overhead of using a database. I don’t if it fits the bill, but you may also want to look into lucene.

I can tell you that Dynamo DB is definitely not a good fit for your use case. There is no fuzzy matching feature and you would need to have an index for each field you want to search or convert your data into a more searchable format for storing in Dynamo, which is something a full text search tool like elasticsearch is going to do for you.

See more
Julien DeFrance
Principal Software Engineer at Tophatter · | 3 upvotes · 6.5K views

The Amazon Elastic Search service will certainly help you do most of the heavy lifting and you won't have to maintain any of the underlying infrastructure. However, elastic search isn't trivial in nature. Typically, this will mean several days worth of work.

Over time and projects, I've over the years leveraged another solution called Algolia Search. Algolia is a fully managed, search as a service solution, which also has SDKs available for most common languages, will answer your fuzzy search requirements, and also cut down implementation and maintenance costs significantly. You should be able to get a solution up and running within a couple of minutes to an hour.

See more
Roel van den Brand
Lead Developer at Di-Vision Consultion · | 3 upvotes · 8.1K views
Recommends
Amazon Athena

Maybe you can do it with storing on S3, and query via Amazon Athena en AWS Glue. Don't know about the performance though. Fuzzy search could otherwise be done with storing a soundex value of the fields you want to search on in a MongoDB. In DynamoDB you would need indexes on every searchable field if you want it to be efficient.

See more
View all (3)
Rana Usman Shahid
Chief Technology Officer at TechAvanza · | 5 upvotes · 123.1K views
Needs advice
on
Firebase
Elasticsearch
and
Algolia

Hey everybody! (1) I am developing an android application. I have data of around 3 million record (less than a TB). I want to save that data in the cloud. Which company provides the best cloud database services that would suit my scenario? It should be secured, long term useable, and provide better services. I decided to use Firebase Realtime database. Should I stick with Firebase or are there any other companies that provide a better service?

(2) I have the functionality of searching data in my app. Same data (less than a TB). Which search solution should I use in this case? I found Elasticsearch and Algolia search. It should be secure and fast. If any other company provides better services than these, please feel free to suggest them.

Thank you!

See more
Replies (2)
Josh Dzielak
Co-Founder & CTO at Orbit · | 5 upvotes · 91.9K views
Recommends
Algolia

Hi Rana, good question! From my Firebase experience, 3 million records is not too big at all, as long as the cost is within reason for you. With Firebase you will be able to access the data from anywhere, including an android app, and implement fine-grained security with JSON rules. The real-time-ness works perfectly. As a fully managed database, Firebase really takes care of everything. The only thing to watch out for is if you need complex query patterns - Firestore (also in the Firebase family) can be a better fit there.

To answer question 2: the right answer will depend on what's most important to you. Algolia is like Firebase is that it is fully-managed, very easy to set up, and has great SDKs for Android. Algolia is really a full-stack search solution in this case, and it is easy to connect with your Firebase data. Bear in mind that Algolia does cost money, so you'll want to make sure the cost is okay for you, but you will save a lot of engineering time and never have to worry about scale. The search-as-you-type performance with Algolia is flawless, as that is a primary aspect of its design. Elasticsearch can store tons of data and has all the flexibility, is hosted for cheap by many cloud services, and has many users. If you haven't done a lot with search before, the learning curve is higher than Algolia for getting the results ranked properly, and there is another learning curve if you want to do the DevOps part yourself. Both are very good platforms for search, Algolia shines when buliding your app is the most important and you don't want to spend many engineering hours, Elasticsearch shines when you have a lot of data and don't mind learning how to run and optimize it.

See more
Mike Endale
Recommends
Cloud Firestore

Rana - we use Cloud Firestore at our startup. It handles many million records without any issues. It provides you the same set of features that the Firebase Realtime Database provides on top of the indexing and security trims. The only thing to watch out for is to make sure your Cloud Functions have proper exception handling and there are no infinite loop in the code. This will be too costly if not caught quickly.

For search; Algolia is a great option, but cost is a real consideration. Indexing large number of records can be cost prohibitive for most projects. Elasticsearch is a solid alternative, but requires a little additional work to configure and maintain if you want to self-host.

Hope this helps.

See more
Decisions about Apigee, Divshot, and Elasticsearch
Phillip Manwaring
Developer at Coach Align · | 5 upvotes · 8.8K views

The new pricing model Algolia introduced really sealed the deal for us on this one - much closer to pay-as-you-go. And didn't want to spend time learning more about hosting/optimizing Elasticsearch when that isn't our core business problem - would much rather pay others to solve that problem for us.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Apigee
Pros of Divshot
Pros of Elasticsearch
  • 10
    Highly scalable and secure API Management Platform
  • 5
    Quick jumpstart
  • 5
    Good documentation
  • 3
    Fast and adjustable caching
  • 3
    Easy to use
  • 10
    Awesome CLI
  • 9
    Static Website Hosting
  • 7
    Free
  • 6
    Simple Web Interface
  • 4
    Great Support
  • 3
    Unlimited Apps
  • 1
    Custom domain
  • 1
    Great place to host an Ember app
  • 1
    Travis-CI Deploy Integration
  • 321
    Powerful api
  • 311
    Great search engine
  • 231
    Open source
  • 213
    Restful
  • 200
    Near real-time search
  • 96
    Free
  • 83
    Search everything
  • 54
    Easy to get started
  • 45
    Analytics
  • 26
    Distributed
  • 6
    Fast search
  • 5
    More than a search engine
  • 3
    Great docs
  • 3
    Awesome, great tool
  • 3
    Easy to scale
  • 2
    Intuitive API
  • 2
    Great piece of software
  • 2
    Fast
  • 2
    Nosql DB
  • 2
    Easy setup
  • 2
    Highly Available
  • 2
    Document Store
  • 2
    Great customer support
  • 1
    Reliable
  • 1
    Not stable
  • 1
    Potato
  • 1
    Open
  • 1
    Github
  • 1
    Elaticsearch
  • 1
    Actively developing
  • 1
    Responsive maintainers on GitHub
  • 1
    Ecosystem
  • 1
    Scalability
  • 0
    Easy to get hot data
  • 0
    Community

Sign up to add or upvote prosMake informed product decisions

Cons of Apigee
Cons of Divshot
Cons of Elasticsearch
  • 6
    Expensive
    Be the first to leave a con
    • 6
      Diffecult to get started
    • 5
      Resource hungry
    • 4
      Expensive
    • 3
      Hard to keep stable at large scale

    Sign up to add or upvote consMake informed product decisions

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

    What is Apigee?

    API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world.

    What is Divshot?

    Divshot makes building and hosting front-end web applications simple. Build locally and deploy using a simple command-line interface. Divshot supports multiple environments, pushState routing, atomic deploys, and more.

    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).

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

    What companies use Apigee?
    What companies use Divshot?
    What companies use Elasticsearch?

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

    What tools integrate with Apigee?
    What tools integrate with Divshot?
    What tools integrate with Elasticsearch?
      No integrations found

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

      Blog Posts

      May 21 2019 at 12:20AM

      Elastic

      +4
      12
      2867
      +42
      46
      38951
      +47
      46
      68578
      +30
      25
      14887
      +26
      19
      4561
      What are some alternatives to Apigee, Divshot, and Elasticsearch?
      Mashery
      Sign In and discover new APIs from our open data commons of RESTful APIs. Mashery's API management offerings include strategic consulting & developer support to help you build your business.
      Zuul
      It is the front door for all requests from devices and websites to the backend of the Netflix streaming application. As an edge service application, It is built to enable dynamic routing, monitoring, resiliency, and security. Routing is an integral part of a microservice architecture.
      Kong
      Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.
      WSO2
      It delivers the only complete open source middleware platform. With its revolutionary componentized design, it is also the only open source platform-as-a-service for private and public clouds available today. With it, seamless migration and integration between servers, private clouds, and public clouds is now a reality.
      Istio
      Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.
      See all alternatives
      How developers use Apigee, Divshot, and Elasticsearch
      imgur uses
      Elasticsearch

      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.

      Instacart uses
      Elasticsearch

      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.

      AngeloR uses
      Elasticsearch

      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.

      Keen uses
      Divshot

      Keen uses Divshot to host internal and customer-facing analytics dashboards. We develop locally with the Divshot CLI and then use it to deploy. It’s great to have one tool that does both. The web interface is handy when you can’t get to the command line. Overall we’re really happy with Divshot – our static site workflow is better and more accessible than ever!

      Brandon Adams uses
      Elasticsearch

      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.

      Ana Phi Sancho uses
      Elasticsearch

      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.

      DivShot uses
      Divshot

      We dogfood our platform by deploying all of our front-ends to it. Our dashboard, lander, documentation, etc. are all deployed on Divshot.