search

pantsel / konga

More than just another GUI to Kong Admin API
MIT License
4.3k stars 826 forks source link

Feature Request: Cassandra as a new datastore connection option in Konga #143

Open jeremyjpj0916 opened 6 years ago

jeremyjpj0916 commented 6 years ago

With Kong supporting both PostgreSQL and Cassandra, it makes sense for Konga to support both of the databases Kong jives with 💃 . Cassandra is a bit trickier in implementation but I think I have a start going here:

cassandra.txt connections.txt

Would love to be able to ditch my MySQL databases and Opt for an automatic distributed DB that has disaster recovery baked in and scales with ease :) !

chbndrhnns commented 5 years ago

Is there any possibilitiy this issue gets some attention?

pantsel commented 5 years ago

@chbndrhnns , this is something I want to do at some point.

It's a bit tricky since there is no reliable adapter for Cassandra available.

That means that I will have to implement it from scratch and something like that requires time that I'm afraid I do not have available at this point.

That being said, although it is a requested feature that will add value to the project, it's low on my priorities for now.

chbndrhnns commented 5 years ago

Hey, am I right that the database is only used for storing the Konga users and the connection and that all interactions with Kong are done via it's API?

Then it would be possible to create a separate SQL database for user management and still use Kong with a Cassandra backend...

pantsel commented 5 years ago

Ofcourse. Konga's db has no impact on Kong, plus, you can easily use Konga without a DB (it uses a file storage build in DB) as long as the kongadata folder is persistant.

Konga uses it's DB mainly for storing users and connections.