redis3m alternatives and similar libraries
Based on the "Database" category
-
SQLite
A completely embedded, full-featured relational database in a few 100k that you can include right into your project. [PublicDomain] -
cpp_redis
C++11 Lightweight Redis client: async, thread-safe, no dependency, pipelining, multi-platform. -
SimDB
High performance, shared memory, lock free, cross platform, single file, minimal dependencies, C++11 key-value store [Apache2]
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of redis3m or a related project?
Popular Comparisons
-
redis3mvsHiredis
-
redis3mvsClickHouse
-
redis3mvscpp_redis
-
redis3mvsRethinkDB driver for C++
-
redis3mvsLMDB++
|
SaaSHub - Software Alternatives and Reviews
View more from us
|
README
redis3m
A C++ Redis client, born to bring my experience using Redis and C++ on a opensource library.
Main goals
- Provide a simple and efficient wrapper of hiredis, with C++ facilities like memory management
- A connection pooling system, with support for high availability using sentinel
- A set of useful patterns ready to use and composable with other code. For example scheduler, orm, counters or message queueing
Dependencies
redis3m requires hiredis and boost libraries.
Install
First step install all required dependencies, on a Debian system you can use:
sudo apt-get install libmsgpack-dev libboost-thread-dev libboost-date-time-dev libboost-test-dev libboost-filesystem-dev libboost-system-dev libhiredis-dev cmake build-essential libboost-regex-dev
Then checkout the code and compile it
git clone https://github.com/luca3m/redis3m
cd redis3m
cmake
make
sudo make install
Documentation
See examples directory for some examples, you can compile them with:
g++ <example.cpp> $(pkg-config --cflags --libs redis3m) -o <example.bin>
You can find all classes reference here
Versioning
This project uses semantic versioning. In short words versions are named X.Y[.Z]. Changing X means break API changes, Y means new features without breaking old code, Z means bug fixing.