What protocols does Dubbo support

What protocols does Dubbo support, and what are their advantages and disadvantages?
Dubbo: Single long connection and NIO asynchronous communication, suitable for large concurrent service calls with small data volume, and consumers are much larger than providers. Transmission protocol TCP, asynchronous Hessian serialization. Dubbo recommends using the dubbo protocol.
RMI: The JDK standard RMI protocol is used. The transmission parameters and return parameter objects need to implement the Serializable interface, use the Java standard serialization mechanism, use blocking short connections, and transmit data packet sizes mixed. The number of consumers and providers is almost the same. Transfer files, the transfer protocol TCP. Multiple short connection TCP protocol transmission, synchronous transmission, suitable for conventional remote service calls and RMI interoperability. In the Common-Collections package that relies on a lower version, Java serialization has security vulnerabilities. WebService: Remote call protocol based on WebService, integrated with CXF implementation, providing interoperability with native WebService. Multiple short connections, based on HTTP transmission, synchronous transmission, suitable for system integration and cross-language calls.
HTTP: The remote invocation protocol based on Http form submission is implemented using Spring's HttpInvoke. Multiple short connections, HTTP transmission protocol, mixed size of incoming parameters, more providers than consumers, need to be called by the application and browser JS. Hessian: Integrated Hessian service, based on HTTP communication, using Servlet to expose service, Dubbo embeds Jetty as the server by default, and provides interoperability with Hession service. Multiple short connections, synchronous HTTP transmission, Hessian serialization, large incoming parameters, the provider is larger than the consumer, the provider is under greater pressure, and files can be transferred.
Memcache: RPC protocol based on Memcache implementation.
Redis: RPC protocol based on Redis implementation.