Distributed-LRU-Cache VS Atomix

Compare Distributed-LRU-Cache vs Atomix and see what are their differences.

Distributed-LRU-Cache

Implementation of a distributed caching solution (LRU : Least recently used) using ZooKeeper. (by zakariamaaraki)

Atomix

A Kubernetes toolkit for building distributed applications using cloud native principles (by atomix)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Distributed-LRU-Cache Atomix
1 1
7 2,346
- 0.1%
0.0 7.8
about 2 years ago 5 months ago
Java Go
MIT License Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Distributed-LRU-Cache

Posts with mentions or reviews of Distributed-LRU-Cache. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Distributed-LRU-Cache yet.
Tracking mentions began in Dec 2020.

Atomix

Posts with mentions or reviews of Atomix. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-28.
  • How to Achieve Geo-redundancy with Zeebe
    2 projects | dev.to | 28 Jun 2022
    To understand how we can achieve resilience in Zeebe, you first need to understand how Zeebe does replication. Zeebe uses distributed consensus — more specifically theRaft Consensus Algorithm — for replication.There is an awesomevisual explanation of the Raft Consensus Algorithm available online, so I will not go into all the details here. The basic idea is that there is a single leader and a set of followers. The most common setup is to have one leader and two followers, and you’ll see why soon.

What are some alternatives?

When comparing Distributed-LRU-Cache and Atomix you can also consider the following projects:

Hazelcast - Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.

Apache ZooKeeper - Apache ZooKeeper

Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM

JGroups - The JGroups project

Redisson - Redisson - Easy Redis Java client with features of In-Memory Data Grid. Sync/Async/RxJava/Reactive API. Over 50 Redis based Java objects and services: Set, Multimap, SortedSet, Map, List, Queue, Deque, Semaphore, Lock, AtomicLong, Map Reduce, Bloom filter, Spring Cache, Tomcat, Scheduler, JCache API, Hibernate, RPC, local cache ...

Spring Boot - Spring Boot

Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM

ScaleCube - Microservices library - scalecube-services is a high throughput, low latency reactive microservices library built to scale. it features: API-Gateways, service-discovery, service-load-balancing, the architecture supports plug-and-play service communication modules and features. built to provide performance and low-latency real-time stream-processing

Apache Storm - Apache Storm

Hystrix - Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.

Copycat

Pinpoint - APM, (Application Performance Management) tool for large-scale distributed systems.