FgForrest
Try alternative gRPC library
Try to benchmark https://armeria.dev/ gRPC library and run performance tests against it. With none or a little performance toll, we should try to integrate it into evitaDB and replace the currently used one. This Armeria gRPC library could offer us many nice-to-have features (such as OpenAPI like documentation endpoint with playground for testing calls, implicit support for grpc-web standard,...) and much easier manipulation with gRPC-related structures.
As far as I understand, the JPMS-related blocker has been resolved in the recent Armeria versions. Would there be anything Armeria team could help with? We'd be happy to address any remaining issues for adoption.
Hi @trustin - we're really positively surprised by your attitude and thank you very much for the support. The problem is currently on our side - we had to lower the priority for this issue due to other commercially important things. But we're planning to resume work on it by the end of May. The Armeria server could help us unify and simplify our internal infrastructure, so we see it as a way forward. We also want to update our performance tests and see what the impact of moving to the new solution will be and let you know the results.
Migration to Armeria server merged to dev branch (canary). It will be base for 2024.10