The reason for Cassandra is the normal reasons someone would turn to Cassandra, fault tolerance, scalability, high write throughput. It's a powerful database we really like but can get a bad rap at times so with Stargate we wanted to make it easier for developers to get their data in and out with their preferred interface. Although we have left it open to extension so if Cassandra isn't your cup of tea we welcome PRs to add new persistence backends.
Example docker-compose and helm charts are definitely in the works! Stay tuned and we should have those out soon.
Oh that looks cool! I'm digging the UI. Thanks for sharing, I'll have to try that out later and maybe we can learn some things from each other.
This is very cool, and I really look forward to the future of the project. Have you thought about formalizing your API spec as an RFC? I generally think that the future of data is to allow complete access to all of your data on user programmatically, and this looks like an amazing tool that would help organizations accomplish exactly that. For example, a user story could be "I want to access then delete all of my comments on Facebook", or "I want to build an application that lets users view their data on Facebook as if it were an Excel spreadsheet".
Any advantages of having Cassandra as underlying db ? An example docker-compose would help to try it out quickly.
We[1] are in similar space but mostly for SQL databases. With automatic APIs we do provide GUI for schema management.
https://github.com/xgenecloud/xgenecloud