Alternatives to CQEngine logo

Alternatives to CQEngine

Lucene, Redis, Hazelcast, Aerospike, and SAP HANA are the most popular alternatives and competitors to CQEngine.
3
20
+ 1
0

What is CQEngine and what are its top alternatives?

It is a NoSQL indexing and Query Engine, for retrieving objects matching SQL-like queries from Java collections, with ultra-low latency
CQEngine is a tool in the In-Memory Databases category of a tech stack.
CQEngine is an open source tool with 1.7K GitHub stars and 248 GitHub forks. Here’s a link to CQEngine's open source repository on GitHub

Top Alternatives to CQEngine

  • Lucene
    Lucene

    Lucene Core, our flagship sub-project, provides Java-based indexing and search technology, as well as spellchecking, hit highlighting and advanced analysis/tokenization capabilities. ...

  • Redis
    Redis

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams. ...

  • Hazelcast
    Hazelcast

    With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution. ...

  • Aerospike
    Aerospike

    Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees. ...

  • SAP HANA
    SAP HANA

    It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk. ...

  • Apache Ignite
    Apache Ignite

    It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale ...

  • MemSQL
    MemSQL

    MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines. ...

  • NCache
    NCache

    NCache is an open source distributed cache for .NET & .NET Core (Apache 2.0) by Alachisoft. NCache provides an extremely fast and linearly scalable distributed cache that caches application data and reduces expensive database trips. ...

CQEngine alternatives & related posts

Lucene logo

Lucene

167
229
2
A high-performance, full-featured text search engine library written entirely in Java
167
229
+ 1
2
PROS OF LUCENE
  • 1
    Fast
  • 1
    Small
CONS OF LUCENE
    Be the first to leave a con

    related Lucene posts

    Shared insights
    on
    SolrSolrLuceneLucene
    at

    "Slack provides two strategies for searching: Recent and Relevant. Recent search finds the messages that match all terms and presents them in reverse chronological order. If a user is trying to recall something that just happened, Recent is a useful presentation of the results.

    Relevant search relaxes the age constraint and takes into account the Lucene score of the document — how well it matches the query terms (Solr powers search at Slack). Used about 17% of the time, Relevant search performed slightly worse than Recent according to the search quality metrics we measured: the number of clicks per search and the click-through rate of the search results in the top several positions. We recognized that Relevant search could benefit from using the user’s interaction history with channels and other users — their ‘work graph’."

    See more
    Redis logo

    Redis

    57.9K
    44.6K
    3.9K
    Open source (BSD licensed), in-memory data structure store
    57.9K
    44.6K
    + 1
    3.9K
    PROS OF REDIS
    • 886
      Performance
    • 542
      Super fast
    • 513
      Ease of use
    • 444
      In-memory cache
    • 324
      Advanced key-value cache
    • 194
      Open source
    • 182
      Easy to deploy
    • 164
      Stable
    • 155
      Free
    • 121
      Fast
    • 42
      High-Performance
    • 40
      High Availability
    • 35
      Data Structures
    • 32
      Very Scalable
    • 24
      Replication
    • 22
      Great community
    • 22
      Pub/Sub
    • 19
      "NoSQL" key-value data store
    • 16
      Hashes
    • 13
      Sets
    • 11
      Sorted Sets
    • 10
      NoSQL
    • 10
      Lists
    • 9
      Async replication
    • 9
      BSD licensed
    • 8
      Bitmaps
    • 8
      Integrates super easy with Sidekiq for Rails background
    • 7
      Keys with a limited time-to-live
    • 7
      Open Source
    • 6
      Lua scripting
    • 6
      Strings
    • 5
      Awesomeness for Free
    • 5
      Hyperloglogs
    • 4
      Transactions
    • 4
      Outstanding performance
    • 4
      Runs server side LUA
    • 4
      LRU eviction of keys
    • 4
      Feature Rich
    • 4
      Written in ANSI C
    • 4
      Networked
    • 3
      Data structure server
    • 3
      Performance & ease of use
    • 2
      Dont save data if no subscribers are found
    • 2
      Automatic failover
    • 2
      Easy to use
    • 2
      Temporarily kept on disk
    • 2
      Scalable
    • 2
      Existing Laravel Integration
    • 2
      Channels concept
    • 2
      Object [key/value] size each 500 MB
    • 2
      Simple
    CONS OF REDIS
    • 15
      Cannot query objects directly
    • 3
      No secondary indexes for non-numeric data types
    • 1
      No WAL

    related Redis posts

    Robert Zuber

    We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

    As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

    When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

    See more

    I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

    We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

    Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

    We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

    Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

    See more
    Hazelcast logo

    Hazelcast

    346
    467
    59
    Clustering and highly scalable data distribution platform for Java
    346
    467
    + 1
    59
    PROS OF HAZELCAST
    • 11
      High Availibility
    • 6
      Distributed Locking
    • 6
      Distributed compute
    • 5
      Sharding
    • 4
      Load balancing
    • 3
      Map-reduce functionality
    • 3
      Simple-to-use
    • 3
      Written in java. runs on jvm
    • 3
      Publish-subscribe
    • 3
      Sql query support in cluster wide
    • 2
      Optimis locking for map
    • 2
      Performance
    • 2
      Multiple client language support
    • 2
      Rest interface
    • 1
      Admin Interface (Management Center)
    • 1
      Better Documentation
    • 1
      Easy to use
    • 1
      Super Fast
    CONS OF HAZELCAST
    • 4
      License needed for SSL

    related Hazelcast posts

    Aerospike logo

    Aerospike

    198
    283
    48
    Flash-optimized in-memory open source NoSQL database
    198
    283
    + 1
    48
    PROS OF AEROSPIKE
    • 16
      Ram and/or ssd persistence
    • 12
      Easy clustering support
    • 5
      Easy setup
    • 4
      Acid
    • 3
      Scale
    • 3
      Performance better than Redis
    • 3
      Petabyte Scale
    • 2
      Ease of use
    CONS OF AEROSPIKE
      Be the first to leave a con

      related Aerospike posts

      Gagan Jakhotiya
      Engineering Manager at BigBasket · | 5 upvotes · 56.4K views
      Shared insights
      on
      Tile38Tile38MySQLMySQLAerospikeAerospike

      I have a very limited but significant use case for spatial index in a routing service. I see these indexes not growing beyond 10,000 geometries for the next 1 year and maybe 100,000 for the next 3 years. The solution needs to be approached from a delivery timeline perspective mostly because the use case also comes with a slightly relaxed compute time SLA and cost optimum implementation PoV.

      We have chosen R-Tree based index as a suitable choice for our use case. We are already using Aerospike and MySQL in our stack. MySQL supports R-Tree and has good docs as well. I couldn't find anything specific to R-Tree with Aerospike. Also, generally would like to understand from the performance perspective how these two choices would fare with something like Tile38?

      Suggestions beside these are also most welcome.

      See more
      SAP HANA logo

      SAP HANA

      158
      138
      27
      An in-memory, column-oriented, relational database management system
      158
      138
      + 1
      27
      PROS OF SAP HANA
      • 5
        In-memory
      • 5
        SQL
      • 4
        Distributed
      • 4
        Performance
      • 2
        Realtime
      • 2
        Concurrent
      • 2
        OLAP
      • 2
        OLTP
      • 1
        JSON
      CONS OF SAP HANA
        Be the first to leave a con

        related SAP HANA posts

        Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

        We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

        We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

        ASP.NET / Node.js / Laravel. ......?

        Please guide us

        See more
        Apache Ignite logo

        Apache Ignite

        93
        164
        32
        An open-source distributed database, caching and processing platform
        93
        164
        + 1
        32
        PROS OF APACHE IGNITE
        • 4
          Multiple client language support
        • 4
          Written in java. runs on jvm
        • 4
          Free
        • 4
          High Avaliability
        • 3
          Load balancing
        • 3
          Sql query support in cluster wide
        • 3
          Rest interface
        • 2
          Easy to use
        • 2
          Distributed compute
        • 2
          Better Documentation
        • 1
          Distributed Locking
        CONS OF APACHE IGNITE
          Be the first to leave a con

          related Apache Ignite posts

          MemSQL logo

          MemSQL

          82
          182
          32
          Database for real-time transactions and analytics.
          82
          182
          + 1
          32
          PROS OF MEMSQL
          • 8
            Distributed
          • 4
            Realtime
          • 3
            Sql
          • 3
            Concurrent
          • 3
            JSON
          • 3
            Columnstore
          • 2
            Scalable
          • 2
            Ultra fast
          • 1
            Availability Group
          • 1
            Mixed workload
          • 1
            Pipeline
          • 1
            Unlimited Storage Database
          CONS OF MEMSQL
            Be the first to leave a con

            related MemSQL posts

            NCache logo

            NCache

            69
            38
            0
            In-Memory Distributed Cache
            69
            38
            + 1
            0
            PROS OF NCACHE
              Be the first to leave a pro
              CONS OF NCACHE
                Be the first to leave a con

                related NCache posts