Details

    • Branch Version/s:
      7.0.x
    • Backported to Branch:
      Committed

      Description

      Our default distribution provider will be based in Http2

      The main innovation Http2 introduces with respect to its predecessor (Http 1.1) is the separation of the connection management concerns (Layer 4) from the concerns of transmitting messages (Layer 5). Messages can be now multiplexed, reordered and cancelled, eliminating bottlenecks and improving the performance and reliability of the application

      We are not going to build everything from scratch but we will reuse some of the pieces that the gRPC project (http://www.grpc.io) offers. It's an active project and it's been recently adopted under the Cloud Native Foundation's umbrella

      It's powered by Netty, probably the best async networking programming framework you can find out there for the JVM

      Since we don't want to force our clients to write their own IDL and modify the way they write their applications we are going to provide a mechanism to scan the services that needs to be exported as remote service and, as said before, some of the existing functionality provided by the gRPC project

      This layer will allow to register clients and servers (depending if you're exporting or importing a service) and send binary messages across the network using Http2

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since last comment:
                2 years, 29 weeks, 4 days ago

                Packages

                Version Package
                7.0.X EE
                Master