Database Failover

[olivierACRI]

Hi,
First of all, this sounds a great project. But I think there is a lot of feature that can make it key inside an infrastructure.
For instance, the failover, as a central point of connection, it should be possible to give a list of servers that can serve as replacement if the main one is not responding. For instance a master postgres and a slave are in sync and the master crashes. This failover mechanism will allow to have an application working in degraded mode hitting the slave in read only. We can also imagine that all write requests are kept and replayed once the master is back (this is a tricky point and needs a lot of discussion, limits...)

[olivierACRI]

Another solution could be to allow a live reload of the configuration, then we can write a tool checking the state of the application, but it needs to restart the gateway....

[mostafa]

Hey @olivierACRI,

Thanks for the awesome suggestions and ideas. Fail-over is the focus of the next milestone: v0.9.x.

I'd be happy to discuss them further if you are interested in collaborating (contributing to the project). Just connect on LinkedIn and we can discuss it there.

[olivierACRI]

Hi @mostafa,
I think your next milestone is quite big, do you have other people interested in those feature, maybe better to prioritize according to common need. Is service Mesh a need, I put your project in balanced with LinkerD which is a proxy but generic one and implement a service mesh as well. Regarding the contribution, I would love but I am not a Go developer, so I need first to rampup on the language. I will connect tonight

[mostafa]

@olivierACRI

Not all the tickets are implementation tickets. Some are epics for investigation (spike) and based on the investigation we will decide what to do next. Also, twelve developers, DevOps and AI/ML specialists showed interest and I already had talks with eight of them. Some of them already started working on tickets, like this one. Would be happy to connect with you as well, so we can collaborate.