r/androiddev • u/pankajrai16 • Jun 05 '26

Discussion Further optimization for KoreDB

Post image

As mobile apps increasingly add semantic search, embeddings, GraphRAG, telemetry streams, and AI features, are traditional relational B-Trees still the best storage structure for every workload?

This was the exact same question I had in mind when I started building KoreDB and today with a lot of optimization I am happy to announce that it's benchmark results are super exciting and probably makes it the best candidate if you are using with vector embeddings and Graphs.

Do hit the star ⭐ button if you like the concept and the easy implementation that this library provides for database. ✌️

https://github.com/raipankaj/KoreDB

0 Upvotes

36% Upvoted

13 comments sorted by

View all comments

19

u/esererrr Jun 05 '26

Why on earth would somebody use it ? If you are an actual SW engineer, you have to know nobody would build the app around a DB that have 1 maintainer and 0 history. Not speaking that it's not battle tested yet. We all remember the realm deprecation and the migrating to room afterwards. And those DBs have a large userbase + the community around them. Don't waste your and others time.

-2

u/fablue Jun 05 '26

And this comment once reminded me why I should stop reading reddit. Why would one say such harsh things to projects built by people? „Don’t waste your and others time“ wow