3 ms·
Directing specific queries to a write connection (dbserver) vs directing requests to specific application servers (potentially mid-request) does seem operationa
by jsmeaton 4y ago
Directing specific queries to a write connection (dbserver) vs directing requests to specific application servers (potentially mid-request) does seem operationally “harder” though.
I’m coming at this from the perspective of a traditional django app that has .using(“write”) when wanting to write data. Otherwise you’re replaying requests at a completely different app server.
Am I understanding this correctly?
- lucasyvas 4y agoThis may or may not be that hard, depending on your server. You could proxy all "mutation" HTTP verbs to your one writer instance, and probably do similar if you are using GraphQL. If you are using something like gRPC I feel this might be more complicated because it's not obvious which actions are read/write. I'm in the same boat as you though overall - I'm not sure what the ideal strategy is, or if one even exists, since this seems to create a problem that does not normally exist. If you are greenfield, maybe you create one service that only does writes - this may be CQRS-like.