Alternatives to Dejavu logo

Alternatives to Dejavu

Kibana, Algolia, Elastic, Mirage, and Searchkit are the most popular alternatives and competitors to Dejavu.
18
36
+ 1
6

What is Dejavu and what are its top alternatives?

dejaVu fits the unmet need of being a hackable data browser for Elasticsearch. Existing browsers were either built with a legacy UI and had a lacking user experience or used server side rendering (I am looking at you, Kibana).
Dejavu is a tool in the Search Tools category of a tech stack.
Dejavu is an open source tool with 7.2K GitHub stars and 462 GitHub forks. Here鈥檚 a link to Dejavu's open source repository on GitHub

Top Alternatives to Dejavu

  • Kibana

    Kibana

    Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch. ...

  • Algolia

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

  • Elastic

    Elastic

    Elastic is an Elasticsearch client for the Go programming language.

  • Mirage

    Mirage

    The Elasticsearch query DSL supports 100+ query APIs ranging from full-text search, numeric range filters, geolocation queries to nested and span queries. Mirage is a modern, open-source web based query explorer for Elasticsearch. ...

  • Searchkit

    Searchkit

    Searchkit is a suite of React components that communicate directly with your Elasticsearch cluster. Each component is built in React and is fully customisable to your needs. ...

  • Elassandra

    Elassandra

    Elassandra is a fork of Elasticsearch modified to run on top of Apache Cassandra in a scalable and resilient peer-to-peer architecture. Elasticsearch code is embedded in Cassanda nodes providing advanced search features on Cassandra tables and Cassandra serve as an Elasticsearch data and configuration store. ...

Dejavu alternatives & related posts

Kibana logo

Kibana

12.3K
9.1K
253
Explore & Visualize Your Data
12.3K
9.1K
+ 1
253
PROS OF KIBANA
  • 86
    Easy to setup
  • 61
    Free
  • 44
    Can search text
  • 21
    Has pie chart
  • 13
    X-axis is not restricted to timestamp
  • 8
    Easy queries and is a good way to view logs
  • 6
    Supports Plugins
  • 3
    Dev Tools
  • 3
    More "user-friendly"
  • 3
    Can build dashboards
  • 2
    Easy to drill-down
  • 2
    Out-of-Box Dashboards/Analytics for Metrics/Heartbeat
  • 1
    Up and running
CONS OF KIBANA
  • 5
    Unintuituve
  • 3
    Elasticsearch is huge
  • 3
    Works on top of elastic only
  • 2
    Hardweight UI

related Kibana posts

Tymoteusz Paul
Devops guy at X20X Development LTD | 21 upvotes 路 4M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Patrick Sun
Software Engineer at Stitch Fix | 11 upvotes 路 401.9K views

Elasticsearch's built-in visualization tool, Kibana, is robust and the appropriate tool in many cases. However, it is geared specifically towards log exploration and time-series data, and we felt that its steep learning curve would impede adoption rate among data scientists accustomed to writing SQL. The solution was to create something that would replicate some of Kibana's essential functionality while hiding Elasticsearch's complexity behind SQL-esque labels and terminology ("table" instead of "index", "group by" instead of "sub-aggregation") in the UI.

Elasticsearch's API is really well-suited for aggregating time-series data, indexing arbitrary data without defining a schema, and creating dashboards. For the purpose of a data exploration backend, Elasticsearch fits the bill really well. Users can send an HTTP request with aggregations and sub-aggregations to an index with millions of documents and get a response within seconds, thus allowing them to rapidly iterate through their data.

See more
Algolia logo

Algolia

947
861
695
Developer-friendly API and complete set of tools for building search
947
861
+ 1
695
PROS OF ALGOLIA
  • 125
    Ultra fast
  • 95
    Super easy to implement
  • 73
    Modern search engine
  • 71
    Excellent support
  • 70
    Easy setup, fast and relevant
  • 46
    Typos handling
  • 40
    Search analytics
  • 31
    Designed to search records, not pages
  • 30
    Multiple datacenters
  • 30
    Distributed Search Network
  • 10
    Smart Highlighting
  • 9
    Search as you type
  • 8
    Instantsearch.js
  • 8
    Multi-attributes
  • 6
    Super fast, easy to set up
  • 5
    Amazing uptime
  • 5
    Database search
  • 4
    Realtime
  • 4
    Great documentation
  • 4
    Highly customizable
  • 4
    Github-awesome-autocomple
  • 3
    Powerful Search
  • 3
    Beautiful UI
  • 3
    Places.js
  • 2
    Integrates with just about everything
  • 2
    Awesome aanltiycs and typos hnadling
  • 1
    Fast response time
  • 1
    Smooth platform
  • 1
    Github integration
  • 1
    Developer-friendly frontend libraries
CONS OF ALGOLIA
  • 10
    Expensive

related Algolia posts

Julien DeFrance
Principal Software Engineer at Tophatter | 16 upvotes 路 2.2M views

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
Tim Specht
鈥嶤o-Founder and CTO at Dubsmash | 16 upvotes 路 294.8K views

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
Elastic logo

Elastic

17
22
0
Elasticsearch client for Go
17
22
+ 1
0
PROS OF ELASTIC
    Be the first to leave a pro
    CONS OF ELASTIC
      Be the first to leave a con

      related Elastic posts

      Mirage logo

      Mirage

      14
      35
      1
      GUI for writing Elasticsearch queries
      14
      35
      + 1
      1
      PROS OF MIRAGE
      • 1
        Clean GUI
      CONS OF MIRAGE
        Be the first to leave a con

        related Mirage posts

        Searchkit logo

        Searchkit

        7
        27
        0
        React UI Components for Elasticsearch
        7
        27
        + 1
        0
        PROS OF SEARCHKIT
          Be the first to leave a pro
          CONS OF SEARCHKIT
            Be the first to leave a con

            related Searchkit posts

            Elassandra logo

            Elassandra

            4
            24
            3
            Elasticsearch implemented on top of Cassandra
            4
            24
            + 1
            3
            PROS OF ELASSANDRA
            • 1
              Microservice database and search engine
            • 1
              Multi-master search engine
            • 1
              Well known API
            CONS OF ELASSANDRA
              Be the first to leave a con

              related Elassandra posts