The first releases of the Redka project have been published, aimed at providing a RESP protocol and API compatible with the Redis DBMS, but implemented on top of the SQLite library. Leveraging SQLite additionally allows data access using SQL, for example, for generating reports or analyzing data. ACID transactions are supported. Redka can run as a server, accepting requests over the network, or used as a module for the Go language. The project code is written in Go and is distributed under the BSD license.
Currently, Redka has added support for string and hash types, as well as commands for manipulating string data, keys, transactions, and hashes. For example, commands are available for setting and retrieving one or more string values associated with a key, setting the expiration time for keys, incrementing/decrementing values, searching for keys by pattern, renaming keys, executing a series of commands within a transaction, and rolling back transactions, along with working with fields in hashes.
In the near future, support for lists, sets, and sorted sets is planned to be added. In the long term, the implementation of the HyperLogLog algorithm, capabilities for manipulating geographical coordinates, and commands for interaction using the publish/subscribe model are expected. Support for Lua scripts, authentication, ACL, watch/unwatch functionality, and the ability to operate within multiple server databases is not currently planned. Cluster support (Redis Cluster) and monitoring (Redis Sentinel) will definitely not be implemented.
Performance testing using tools from the Redis project showed that Redka lags behind Redis by 2-6 times due to the lack of specific optimizations for storing data in key/value format. Specifically, in the created test environment, Redis demonstrated performance of 133 thousand SET operations per second and 139 thousand GET operations per second, whereas Redka's performance was 30 thousand SET operations per second and 63 thousand GET operations per second when the database was hosted in memory. When the database was stored on disk, Redka's performance reached 22 thousand SET operations per second and 56 thousand GET operations per second.
Source: opennet.ru
