chiselstore

Can any of the contributors to ChiselStore [1] , mentioned in the article, elaborate on the comment made about it? What's the big deal about not fitting well with SQLx? This isn't a requirement for such a library to be successful. What other problems is it allegedly suffering from? It could be more of a problem of perspective. [1] https://github.com/chiselstrike/chiselstore

there’s some stuff out there: - https://github.com/rqlite/rqlite - https://github.com/chiselstrike/chiselstore - https://dqlite.io/ I’m sure there’s more, those are just the ones I remember.

I've looked at the https://github.com/chiselstrike/chiselstore/blob/main/proto/... - and calling the service "RPC" is not great if this is going to be bundled with other gRPC services - why not call it "chiselStore" or something more concrete? on a 2nd note, each method should have it's own Request Response, and ideally they should be suffixed same way. Returning same proto for multiple methods might break future compatibility - e.g. what if AppendEntries needs to return somehing else than Void? - ideally you make it from the start to return an empty AppendEntriesResponse, and then you can extend that proto. https://developers.google.com/protocol-buffers/docs/proto3#u... (edit again, also the package should not be called just "proto")