Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add gokv.Store implementation for Apache Ignite #64

Closed
philippgille opened this issue Dec 29, 2018 · 1 comment
Closed

Add gokv.Store implementation for Apache Ignite #64

philippgille opened this issue Dec 29, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@philippgille
Copy link
Owner

Apache Ignite seems to be one of the most popular multi-model open source databases. It has a key-value store mode, which seems to be meant to be used as cache, but Apache Ignite seems to be doing everything in-memory first, and then use their "durable memory" or "persistence" components to achieve durability.

The key-value store mode is JCache compliant, see:

Is Ignite a key-value store?

Yes. Ignite provides a feature rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, and .NET.

And: https://ignite.apache.org/use-cases/database/key-value-store.html

The latter link includes the following bullet point regarding the JCache specification:

  • Pluggable Persistence

So this seems to be the optimal way to use Ignite, but on the other hand there don't seem to be any Go packages for JCache. But then again, Ignite supports the Redis protocol (see here), has its own binary protocol (see here) and even a REST API (see here).

@philippgille
Copy link
Owner Author

philippgille commented Dec 29, 2018

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant