awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
olric-data avatar

olric-data/olric

0
View on GitHub↗

Olric

Olric is a distributed data grid and in-memory key-value store that partitions and replicates data across a cluster of servers. It serves as a shared memory system for managing distributed maps, performing atomic operations, and acting as an in-memory data cache.

The system provides a distributed locking mechanism for concurrency control and a pub-sub messaging system that broadcasts and routes messages over named channels across the cluster.

The platform covers wide-ranging capabilities including cluster management and orchestration, data replication with configurable quorums, and automated memory eviction using time-to-live policies. It also includes tools for monitoring cluster health, auditing data distribution, and password-based client authentication.

Olric can be deployed as a standalone independent service, as a container, or integrated directly into an application as an embedded library.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Features

  • Distributed Key-Value Stores - Provides a high-performance distributed key-value store that partitions and replicates data across a cluster of servers.
  • Distributed Key-Value Stores - Stores and retrieves data across a cluster of servers using a distributed hash table.
  • Key-Value Stores - Provides a high-performance in-memory key-value store for distributed data management.
  • Key-Value - Functions as a high-performance distributed store for saving and fetching various data types via unique keys.
  • Distributed Data Management - Partitions data across multiple nodes and manages replicas to ensure high availability and system scalability.
  • Distributed Data Replication - Ensures data availability and consistency across the cluster using quorum-based replication.
  • Data Replication - Synchronizes data across distributed nodes and uses failure detection to maintain reliability.
  • Data Replication Strategies - Copies data to backup owners using synchronous or asynchronous replication for fault tolerance.
  • Quorum-Based Commit Protocols - Guarantees data accuracy by requiring a minimum number of replica acknowledgments for read and write operations.
  • Distributed Data Grids - Provides a shared memory system for managing distributed maps and performing atomic operations across nodes.
  • Distributed Routing Tables - Maintains a distributed routing table that maps data partitions to their primary and replica owners for efficient request routing.
  • In-Memory Caches - Provides an in-memory data cache with automated time-to-live expiration and memory eviction policies.
  • Distributed Memory Caches - Caches transient data in memory across multiple nodes with automated eviction and TTL policies.
  • Model-to-Source Routing - Provides routing information mapping data partitions to specific owner nodes for request dispatching.
  • Quorum-Based Consistency - Requires a minimum number of successful replica operations before returning a result to the client.
  • Cluster Membership Coordination - Tracks active node instances and manages peer discovery to maintain connectivity as nodes join or leave.
  • Cluster Membership Protocols - Uses gossip-based protocols for nodes to discover each other and maintain a dynamic cluster topology.
  • Automated Node Discovery - Automatically identifies and connects to peer nodes using cloud-native plugins and external discovery services.
  • Capacity Scaling - Dynamically adds new nodes to the cluster to increase storage capacity and distribute the workload.
  • Distributed Locks - Provides a distributed locking mechanism to coordinate access to shared resources across the cluster.
  • Cluster Discovery Services - Locates and joins peer nodes by integrating with cloud providers and cluster discovery services.
  • Publish-Subscribe Messaging - Enables producers and consumers to communicate asynchronously via named channels.
  • Data Synchronization and Consistency - Sets read and write quorums to balance system performance against data consistency guarantees.
  • Pub-Sub Messaging - Implements a pub-sub messaging system to broadcast real-time updates across the cluster.
  • Sharded Pub/Sub - Uses glob-style pattern matching to route pub-sub messages to subscribers across the cluster.
  • Publish-Subscribe Systems - Distributes messages using specific channel names or pattern-based subscriptions.
  • Service Discovery Integrations - Integrates with external naming services and daemons to automatically locate peer nodes within a network.
  • Consistent Hashing - Implements consistent hashing to distribute data across nodes and minimize remapping during cluster scaling.
  • Split-Brain Prevention - Prevents data divergence by using majority quorums to stop node operations during network partitions.
  • Distributed Atomic Operations - Supports atomic increments and replacements of values to ensure consistency across the distributed grid.
  • Batch Data Operations - Groups multiple read and write commands into single requests to reduce network overhead.
  • Cache Eviction Policies - Manages memory usage by removing outdated entries using time-based or usage-based policies.
  • Cursor-Based Iteration - Provides cursor-based iteration to retrieve large distributed datasets across partitions without blocking server resources.
  • Conflict Resolution Strategies - Balances throughput and reliability using a combination of quorums and conflict resolution strategies.
  • Database Key Scanning - Provides non-blocking iteration to scan keys in a distributed map using match patterns.
  • Distributed Query Processing - Executes distributed queries to scan and retrieve keys from maps across multiple cluster nodes.
  • Write Conflict Resolution Policies - Resolves data conflicts between diverging versions using a last-write-wins policy based on client timestamps.
  • Conflict Resolution - Compares replica timestamps during reads and propagates the latest version to outdated nodes.
  • Distributed Map Scanning - Enables retrieving subsets of entries from distributed maps using filtering criteria and limits.
  • Cloud Native Orchestration - Automatically discovers peer nodes and manages cluster membership within cloud or containerized environments.
  • Standalone or Cluster Deployments - Supports flexible deployment as either a standalone server or a distributed cluster.
  • Standalone Service Deployments - Can be run as a standalone server accessed via a standard serialization protocol.
  • Split-Brain Prevention Mechanisms - Prevents split-brain scenarios by requiring a majority quorum for node operations during network partitions.
  • Pattern-Based Routing - Distributes pub-sub messages across the cluster using glob-style pattern matching for flexible channel subscriptions.
  • Embedded Library Deployments - Allows the data grid to be integrated directly into applications for low-latency access.
  • Last-Write-Wins Semantics - Reconciles diverging data versions using a last-write-wins policy based on client timestamps.
  • LRU Cache Eviction - Automatically removes the least recently used items from memory to prevent system resource exhaustion.
  • Cluster Health Monitoring - Retrieves operational statistics and runtime metrics to analyze the overall state of the grid.
  • Cluster Monitoring Systems - Tracks network throughput, memory allocation, and connection counts to monitor system health.
  • Cluster Topology Monitors - Provides tools to retrieve the cluster routing table and list all members and roles.
  • Time-To-Live Expirations - Automatically evicts in-memory entries after a specified time-to-live duration to manage resource limits.
3,469 stars·147 forks·Go·Apache-2.0·60 views

Star history

Star history chart for olric-data/olricStar history chart for olric-data/olric

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

Projects sharing features with Olric

These projects share indexed features with Olric. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • hazelcast/hazelcasthazelcast avatar

    hazelcast/hazelcast

    6,570View on GitHub↗

    Hazelcast is a distributed data platform that combines an in-memory data grid with a stream processing engine to support real-time analytics and event-driven applications. It functions as a partitioned, distributed key-value store that replicates data across cluster nodes to provide low-latency access and high availability. The platform also serves as a distributed SQL query engine, allowing users to execute standard SQL statements against both in-memory datasets and external data sources. What distinguishes Hazelcast is its use of a distributed consensus subsystem to maintain strongly consis

    Javabig-datacachingdata-in-motion
    View on GitHub↗6,570
  • nats-io/nats-servernats-io avatar

    nats-io/nats-server

    20,076View on GitHub↗

    NATS Server is a high-performance, lightweight messaging system designed for cloud-native applications, edge computing, and distributed microservices. It functions as a distributed publish-subscribe broker that routes messages using hierarchical, dot-separated subject strings, enabling decoupled communication between services without requiring centralized broker lookups. The system supports core messaging patterns including asynchronous publish-subscribe, request-reply, and load-balanced queue processing. The platform distinguishes itself through a decentralized architecture that eliminates t

    Gocloudcloud-computingcloud-native
    View on GitHub↗20,076
  • apple/foundationdbapple avatar

    apple/foundationdb

    16,446View on GitHub↗

    FoundationDB is an ACID-compliant distributed transactional key-value store. It functions as a scalable database engine that ensures strict serializability and data consistency across a cluster of servers using a shared-nothing architecture. The system is distinguished by its multi-region replication capabilities, allowing data to be synchronized across different datacenters for high availability and disaster recovery. It utilizes optimistic concurrency control to manage distributed transactions and employs a majority-based coordination system to maintain cluster state. The platform provides

    C++aciddistributed-databasefoundationdb
    View on GitHub↗16,446
  • tporadowski/redistporadowski avatar

    tporadowski/redis

    9,987View on GitHub↗

    Redis is a high-performance in-memory key-value store that functions as a distributed cache, message broker, and NoSQL database. It provides sub-millisecond read and write access to data stored in RAM and can operate as a vector database for indexing high-dimensional embeddings. The system supports a wide range of data storage and synchronization primitives, including the management of strings, hashes, lists, sets, and JSON documents. It enables real-time data operations through atomic transactions, hybrid persistence using snapshots and append-only logs, and high-availability configurations

    Credisredis-for-windowsredis-msi-installer
    View on GitHub↗9,987
Compare all 30 related projects→

Frequently asked questions

What does olric-data/olric do?

Olric is a distributed data grid and in-memory key-value store that partitions and replicates data across a cluster of servers. It serves as a shared memory system for managing distributed maps, performing atomic operations, and acting as an in-memory data cache.

What are the main features of olric-data/olric?

The main features of olric-data/olric are: Distributed Key-Value Stores, Key-Value Stores, Key-Value, Distributed Data Management, Distributed Data Replication, Data Replication, Data Replication Strategies, Quorum-Based Commit Protocols.

Which projects share features with olric-data/olric?

Projects with overlapping indexed features include: hazelcast/hazelcast — Hazelcast is a distributed data platform that combines an in-memory data grid with a stream processing engine to… nats-io/nats-server — NATS Server is a high-performance, lightweight messaging system designed for cloud-native applications, edge… apple/foundationdb — FoundationDB is an ACID-compliant distributed transactional key-value store. It functions as a scalable database… tporadowski/redis — Redis is a high-performance in-memory key-value store that functions as a distributed cache, message broker, and NoSQL… doocs/advanced-java — This project is a comprehensive Java backend engineering guide and technical reference focused on high-concurrency… hdt3213/godis — Godis is a Redis-compatible in-memory database and distributed key-value store. It functions as a replicated data…