Details

    • Type: New Feature
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 5.x Backlog
    • Component/s: Reactive, Web
    • Labels:
      None
    • Last commented by a User:
      false

      Description

      gRPC is becoming defacto standard for service to service communication, due to its ubiquitous nature & use of HTTP2

      Currently we have `grpc-java` which generates its own version of classes that handle request in their own proprietary way when compared to Spring MVC & Spring WebFlux.

      Plus, modern service mesh frameworks like https://envoyproxy.io works very nicely with gRPC.

      Developers in spring world requires this high performance, type safe service-service integration (tho we have integration with hystrix, gRPC is much more performant & support wide variety of languages).

      Here are some pain points in using grpc-java in spring world

      1. Since gRPC makes no assumption about Spring web framework, its request handling has a completely different path outside of WebFlux/MVC
      2. Integrating that code with spring ecosystem like Security will be completely adhoc & fragile

      If spring can scaffold a WebFlux/MVC project from grpc service definition, it will improve the development experience & at the sametime developers like me can enjoy the benefits of gRPC

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rstoya05-aop Rossen Stoyanchev
                Reporter:
                thekalinga Ashok
                Last updater:
                Rossen Stoyanchev
              • Votes:
                6 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Days since last comment:
                  26 weeks, 1 day ago