Investigate various possible replacements for Jussi
This is a long term issue to investigate if it makes sense to replace Jussi with alternative technology.
Initial discussion back in April:
wrona 10:45 AM Just fyi: few info related to tools we could use in the future to implement real load balancer and proxy: https://grpc.io/blog/grpc-load-balancing/#load-balancing-options https://cloud.google.com/solutions/exposing-grpc-services-on-gke-using-envoy-proxy https://www.envoyproxy.io/
for the 1st look it seems possible to have support for "old" json calls in front of this proxy, where all further internal communication could use new protobuf based calls. But that are my first thoughts.
efrias 10:50 AM probably not related to what you're talking about, but I've been using envoy on the blocktrades backend for translating between gRPC spoken by the backend into gRPC-Web in the browser, or into ReST for the browser or debugging.
wrona 10:51 AM it is actually similar thing if I get it correctly. I think we should look deeper at it when we decide to focus more on jussi replacement or something
efrias 10:52 AM The documentation for the grpc <-> json translation is pretty bad, but all of the simple stuff I've tried works
dkedzierski 10:55 AM wrona also in case if you need custom solution i have some experience in developing proxies and "man in the middle" stuff