keyvi | It is an in-memory FST | Key Value Database library

 by   KeyviDev C++ Version: 0.6.0 License: Apache-2.0

kandi X-RAY | keyvi Summary

kandi X-RAY | keyvi Summary

keyvi is a C++ library typically used in Database, Key Value Database applications. keyvi has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Keyvi - the short form for "Key value index" is a key value store (KVS) optimized for size and lookup speed. The usage of shared memory makes it scalable and resistant. The biggest difference to other stores is the underlying data structure based on finite state machine. Storage is very space efficient, fast and by design makes various sorts of approximate matching be it fuzzy string matching or geo highly efficient. The immutable FST data structure can be used stand-alone for static datasets. If you need online writes, you can use keyvi index, a near realtime index. The index can be used as embedded key value store, e.g. if you already have a network stack in your application. A out of the box network enabled store is available with keyvi-server.

            kandi-support Support

              keyvi has a low active ecosystem.
              It has 189 star(s) with 34 fork(s). There are 9 watchers for this library.
              There were 8 major release(s) in the last 6 months.
              There are 13 open issues and 27 have been closed. On average issues are closed in 150 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of keyvi is 0.6.0

            kandi-Quality Quality

              keyvi has no bugs reported.

            kandi-Security Security

              keyvi has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              keyvi is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              keyvi releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of keyvi
            Get all kandi verified functions for this library.

            keyvi Key Features

            No Key Features are available at this moment for keyvi.

            keyvi Examples and Code Snippets

            No Code Snippets are available at this moment for keyvi.

            Community Discussions


            Laravel how to "properly" store & retrieve models in a Redis hash
            Asked 2021-Jul-08 at 17:02

            I'm developing a Laravel application & started using Redis as a caching system. I'm thinking of caching the data of all of a specific model I have, as a user may make an API request that this model is involved in quite often. Would a valid solution be storing each model in a hash, where the field is that record's unique ID, and the values are just the unique model's data, or is this use case too complicated for a simple key value database like Redis? I"m also curious as to how I would create model instances from the hash, when I retrieve all the data from it. Replies are appreciated!



            Answered 2021-Jul-08 at 17:02

            Short answer: Yes, you can store a model, or collections, or basically anything in the key-value caching of Redis. As long as the key provided is unique and can be retraced. Redis could even be used as a primary database.

            Long answer

            Ultimately, I think it depends on the implementation. There is a lot of optimization that can be done before someone can/should consider caching all models. For "simple" records that involve large datasets, I would advise to first optimize your queries and code and check the results. Examples:

            1. Select only data you need, not entire models.
            2. Use the Database Query Builder for interacting with the database when targeting large records, rather than Eloquent (Eloquent is significantly slower due to the Active Record pattern).
            3. Consider using the toBase() method. This retrieves all data but does not create the Eloquent model, saving precious resources.
            4. Use tools like the Laravel debugbar to analyze and discover potential long query loads.

            For large datasets that do not change often or optimization is not possible anymore: caching is the way to go!

            There is no right answer here, but maybe this helps you on your way! There are plenty of packages that implement similar behaviour.



            Can compacted Kafka topic be used as key-value database?
            Asked 2020-Nov-25 at 01:12

            In many articles, I've read that compacted Kafka topics can be used as a database. However, when looking at the Kafka API, I cannot find methods that allow me to query a topic for a value based on a key.

            So, can a compacted Kafka topic be used as a (high performance, read-only) key-value database?

            In my architecture I want to feed a component with a compacted topic. And I'm wondering whether that component needs to have a replica of that topic in its local database, or whether it can use that compacted topic as a key value database instead.



            Answered 2020-Nov-25 at 01:12

            Compacted kafka topics themselves and basic Consumer/Producer kafka APIs are not suitable for a key-value database. They are, however, widely used as a backstore to persist KV Database/Cache data, i.e: in a write-through approach for instance. If you need to re-warmup your Cache for some reason, just replay the entire topic to repopulate.

            In the Kafka world you have the Kafka Streams API which allows you to expose the state of your application, i.e: for your KV use case it could be the latest state of an order, by the means of queriable state stores. A state store is an abstraction of a KV Database and are actually implemented using a fast KV database called RocksDB which, in case of disaster, are fully recoverable because it's full data is persisted in a kafka topic, so it's quite resilient as to be a source of the data for your use case.

            Imagine that this is your Kafka Streams Application architecture:

            To be able to query these Kafka Streams state stores you need to bundle an HTTP Server and REST API in your Kafka Streams applications to query its local or remote state store (Kafka distributes/shards data across multiple partitions in a topic to enable parallel processing and high availability, and so does Kafka Streams). Because Kafka Streams API provides the metadata for you to know in which instance the key resides, you can surely query any instance and, if the key exists, a response can be returned regardless of the instance where the key lives.

            With this approach, you can kill two birds in a shot:

            1. Do stateful stream processing at scale with Kafka Streams
            2. Expose its state to external clients in a KV Database query pattern style

            All in a real-time, highly performant, distributed and resilient architecture.

            The images were sourced from a wider article by Robert Schmid where you can find additional details and a prototype to implement queriable state stores with Kafka Streams.

            Notable mention:

            If you are not in the mood to implement all of this using the Kafka Streams API, take a look at ksqlDB from Confluent which provides an even higher level abstraction on top of Kafka Streams just using a cool and simple SQL dialect to achieve the same sort of use case using pull queries. If you want to prototype something really quickly, take a look at this answer by Robin Moffatt or even this blog post to get a grip on its simplicity.

            While ksqlDB is not part of the Apache Kafka project, it's open-source, free and is built on top of the Kafka Streams API.


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install keyvi

            You can download it from GitHub.


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • PyPI

            pip install keyvi

          • CLONE
          • HTTPS


          • CLI

            gh repo clone KeyviDev/keyvi

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link