Alternatives to Beringei logo

Alternatives to Beringei

InfluxDB, Redis, Hazelcast, Aerospike, and SAP HANA are the most popular alternatives and competitors to Beringei.
11
40
+ 1
0

What is Beringei and what are its top alternatives?

Beringei is a high performance time series storage engine. Time series are commonly used as a representation of statistics, gauges, and counters for monitoring performance and health of a system.
Beringei is a tool in the In-Memory Databases category of a tech stack.
Beringei is an open source tool with GitHub stars and GitHub forks. Here’s a link to Beringei's open source repository on GitHub

Top Alternatives to Beringei

  • InfluxDB
    InfluxDB

    InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out. ...

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

Beringei alternatives & related posts

InfluxDB logo

InfluxDB

962
1.1K
169
An open-source distributed time series database with no external dependencies
962
1.1K
+ 1
169
PROS OF INFLUXDB
  • 54
    Time-series data analysis
  • 30
    Easy setup, no dependencies
  • 24
    Fast, scalable & open source
  • 21
    Open source
  • 19
    Real-time analytics
  • 6
    Continuous Query support
  • 5
    Easy Query Language
  • 4
    HTTP API
  • 4
    Out-of-the-box, automatic Retention Policy
  • 1
    Offers Enterprise version
  • 1
    Free Open Source version
CONS OF INFLUXDB
  • 4
    Instability
  • 1
    HA or Clustering is only in paid version

related InfluxDB posts

Hi everyone. I'm trying to create my personal syslog monitoring.

  1. To get the logs, I have uncertainty to choose the way: 1.1 Use Logstash like a TCP server. 1.2 Implement a Go TCP server.

  2. To store and plot data. 2.1 Use Elasticsearch tools. 2.2 Use InfluxDB and Grafana.

I would like to know... Which is a cheaper and scalable solution?

Or even if there is a better way to do it.

See more
Redis logo

Redis

51.1K
38.7K
3.9K
Open source (BSD licensed), in-memory data structure store
51.1K
38.7K
+ 1
3.9K
PROS OF REDIS
  • 881
    Performance
  • 538
    Super fast
  • 510
    Ease of use
  • 441
    In-memory cache
  • 321
    Advanced key-value cache
  • 190
    Open source
  • 179
    Easy to deploy
  • 163
    Stable
  • 152
    Free
  • 120
    Fast
  • 40
    High-Performance
  • 39
    High Availability
  • 34
    Data Structures
  • 31
    Very Scalable
  • 23
    Replication
  • 20
    Pub/Sub
  • 20
    Great community
  • 17
    "NoSQL" key-value data store
  • 14
    Hashes
  • 12
    Sets
  • 10
    Sorted Sets
  • 9
    Lists
  • 8
    BSD licensed
  • 8
    NoSQL
  • 7
    Integrates super easy with Sidekiq for Rails background
  • 7
    Async replication
  • 7
    Bitmaps
  • 6
    Keys with a limited time-to-live
  • 6
    Open Source
  • 5
    Strings
  • 5
    Lua scripting
  • 4
    Hyperloglogs
  • 4
    Awesomeness for Free!
  • 3
    Transactions
  • 3
    Runs server side LUA
  • 3
    outstanding performance
  • 3
    Networked
  • 3
    LRU eviction of keys
  • 3
    Written in ANSI C
  • 3
    Feature Rich
  • 2
    Performance & ease of use
  • 2
    Data structure server
  • 1
    Simple
  • 1
    Channels concept
  • 1
    Scalable
  • 1
    Temporarily kept on disk
  • 1
    Dont save data if no subscribers are found
  • 1
    Automatic failover
  • 1
    Easy to use
  • 1
    Existing Laravel Integration
  • 1
    Object [key/value] size each 500 MB
CONS OF REDIS
  • 14
    Cannot query objects directly
  • 2
    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

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

related Hazelcast posts

Aerospike logo

Aerospike

165
248
47
Flash-optimized in-memory open source NoSQL database
165
248
+ 1
47
PROS OF AEROSPIKE
  • 15
    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

    SAP HANA logo

    SAP HANA

    136
    113
    27
    An in-memory, column-oriented, relational database management system
    136
    113
    + 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

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

        related Apache Ignite posts

        MemSQL logo

        MemSQL

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

          related MemSQL posts

          NCache logo

          NCache

          72
          34
          0
          In-Memory Distributed Cache
          72
          34
          + 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