I love the concept but…

[devlzcode]

Does this project know what it wants to be? It does a lot of things so its hard to determine what its best at. If the project continues to try and support every single use case what are the trade offs such as performance, maintenance, features, and all the other costs of being good at all but master of none? Personally, I will definitely try this out on side project it seems to truly be the database of tomorrow, I just hope figures out what it wants to be, preferably the super-powered database.

[devlzcode]

Or perhaps being the jack of all trades is the niche it fits. It doesn't need to be a contender against databases like SQL/Postgres or MongoDB, but its own.

[AlexFrid]

Does this project know what it wants to be?

Yes, we aim to be the default db of tomorrow. This can of course only be accomplished over several years and loads of refinement in the specifics, but it will definitely be a super-powered database 🙌