oxigraph VS skytable

oxigraph

I am currently building a single-node graph database implementing the SPARQL query language. It is written in Rust and is named Oxigraph: https://github.com/oxigraph/oxigraph

I would love to get help, I have a working MVP but there are a lot of work left to get good performances for which I would love help. Some current problems are:

I've recently had to use KDE from Ubuntu 18.04 (Plasma 5.12) and my daily driver is Arch Linux with the current 5.24 beta. Improvement in Plasma is really incredible. Kudos to everyone contributing to make it better. It's such a stable and powerful system.

What's still lacking is unfortunately the application side: baloo indexer ist still a mess that hogs cpu and likes to corrupt itself every other day. Replaced it with mlocate. KDE Mail, Organizer, Akonadi are very powerful concepts and ideas and I hope some talented devs take on them and make them more stable and robust. The approach to use PostgreSQL/MySQL on the desktop has failed maybe there is a lighter way i.e. something like oxigraph (https://github.com/oxigraph/oxigraph) for implementing the Nepomuk/ Semantic Desktop ideas in a fast and stable way. For now I'm using evince and evolution for mail and reading PDFs.

Still hugs and love to everyone involved in Plasma I can't imagine using anything else and lately I'm replacing GNOME with Plasma everywhere I'm allowed to.

Oxigraph might be suitable https://github.com/oxigraph/oxigraph. It has bindings for Python and JavaScript.

I am currently working on an embeddable graph database. It uses the SPARQL query language. It's still WIP but I believe some people already use it on Android. https://github.com/oxigraph/oxigraph

Hey HN!

I've been working on Skytable since 2020 and after several iterations from a simple K/V store, we've walked the path to this release. The goal of Skytable is to deliver a solid foundation for building data intensive applications.

Skytable's primary goal is performance and scale. Even with a query language it can outperform K/V stores which use simple commands (benchmarks will be shared in another post).

Several implementations in Skytable (especially around query evaluation and execution) are fundamentally different from SQL and even NoSQL counterparts and there are some entirely new concepts which might make it a little hard to grasp.

BlueQL is a very important part of Skytable and it employs some interesting concepts to try and reduce the surface for injection attacks and tries to be a modern and secure alternative to SQL.

- Source code: https://github.com/skytable/skytable

For those who were looking for the source code, here's the link: https://github.com/skytable/skytable

Link to source code: https://github.com/skytable/skytable

Here are some quick links: - Source code: https://github.com/skytable/skytable - Rust driver: https://github.com/skytable/client-rust

I think this is relevant... These are 3 OSS databases that can be an alternative to Redis:

- KeyDB: https://github.com/snapchat/keydb

- Dragonfly: https://github.com/dragonflydb/dragonfly

- Skytable: https://github.com/skytable/skytable

I have used keyDB before. The raft consensus makes building an HA Redis easy.

:) in fact, I copied the definition from the project page and Skytable is not finished project yet. You can see here, the real time features in the road map. https://github.com/skytable/skytable/issues/203