You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 3, 2022. It is now read-only.
Alexandre Stein edited this page Aug 3, 2018
·
2 revisions
Intro
In a clustered and/or a replicated environment services needs to speaks to each others.
In some database the number of open ports is pretty impressive. For example in CouchBase (a database which I really like) you have plage of ports and so many open ports.
Take a look at it.
I think this is some kind of issue.
Possible solution
QUIC
QUIC is a communication protocol.
We can make all needed connections goes to one open port.
QUIC gives the power of using rich HTTP API with low latency and optimized bandwidth with multiplex.
No need to open many ports, all needed information can be set inside the headers like type of transmission, authentication and any kind of informations.
Because QUIC provides a HTTP server, we can expose a standard TCP HTTP as a fallback to clients which can't handle QUIC.
quic-go package looks like a really good starting point to work with.