Releases: buraksezer/olric
v0.5.7
v0.5.6
v0.5.5
Olric is a distributed, in-memory object store. It's designed from the ground up to be distributed, and it can be used both as an embedded Go library and as a language-independent service.
With Olric, you can instantly create a fast, scalable, shared pool of RAM across a cluster of computers.
Olric is implemented in Go and uses the Redis serialization protocol. So Olric has client implementations in all major programming languages.
Olric is highly scalable and available. Distributed applications can use it for distributed caching, clustering and publish-subscribe messaging.
It is designed to scale out to hundreds of members and thousands of clients. When you add new members, they automatically discover the cluster and linearly increase the memory capacity. Olric offers simple scalability, partitioning (sharding), and re-balancing out-of-the-box. It does not require any extra coordination processes. With Olric, when you start another process to add more capacity, data and backups are automatically and evenly balanced.
This release includes the following fixes and improvements:
- Fix a minor data race issue in cluster events.
v0.5.4
v0.5.3
This release includes the following fixes and improvements:
- Fix a data race between parallel GET calls,
- Upgrade redcon to v1.6.2.
v0.5.2
v0.5.1
v0.5.0
Olric v0.5.0 is here.
- Olric Binary Protocol has been replaced with Redis Serialization Protocol 2 (RESP2),
- Redefined DMap API,
- Improved storage engine,
- Cluster events,
- A drop-in replacement of Redis' Publish-Subscribe messaging. DTopic data structure has been removed,
olric-cli
,olric-benchmark
, andolric-stats
has been removed.
Important: Please note that this version of Olric is incompatible with the previous versions.
See the README.md file and the documents on pkg.go.dev.
v0.4.10
v0.4.9
This release includes the following fixes and improvements:
buraksezer/consistent upgraded to v0.10.0
. It includes the following fixes:
- AverageLoad() function panics with "divide by zero" when no members are in the hash ring buraksezer/consistent#19,
- RLock called twice in GetClosestN and cause a deadlock buraksezer/consistent#23,
- Improve documentation,
- Validate configuration and add default values to the configuration variables.