We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would it be possible to use protobuf in addition to json.
nats as inherent support for protocol buffers .
Looks like an amazingly simple and clean system btw - well done
The text was updated successfully, but these errors were encountered:
I am working on hooking up mongodb so that a change in mongodb ripples through resgate.
the protocol I used is based on protobufs but I can convert to json on the fly .
I am just worried that is a field / renamed is added in mongodb the end clients will break ? Renaming especially ..
Sorry, something went wrong.
This does help in terms of architectural changes to the protocol .
go-res/service.go
Line 18 in d5ebd39
am more worried about data schema changes from source db. Is there s concept of this in go-res ?
No branches or pull requests
Would it be possible to use protobuf in addition to json.
nats as inherent support for protocol buffers .
Looks like an amazingly simple and clean system btw - well done
The text was updated successfully, but these errors were encountered: