OkHttp VS Netty

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

OkHttp

Being more familiar with Android development only, I mainly use https://github.com/square/okhttp/tree/master/mockwebserver

Retrofit is the best library that lets you connect to HTTP-based API services from your Android applications. It leverages the OkHttp library’s core functionality, adding a bunch of features to it while eliminating the boilerplate code.

Use Retrofit or anything else that builds on OkHttp. If you do end up needing some features that Cronet supports but OkHttp doesn't (such as HTTP/3), just write an interceptor or use google/cronet-transport-for-okhttp.

Even as of 2022, there are networks out there that have broken/misconfigured IPv6, and there most likely always will be. Some wireless carriers and ISPs support it, but in some cases, people have old or improperly-configured routers and devices. Patchy IPv6 support is less of a problem on iOS and the web these days since those clients have support for dynamically falling back on IPv4 when IPv6 fails. After more research, we realized that Android didn’t have this “dual-stack” IP support, and neither did our preferred networking library, OkHttp. This explained why the content-loading issues only surfaced on Android, and why it took some additional digging to uncover the root cause.

Working with the reddit infrastructure team, we did more testing and built high confidence that this last IPv6 theory was indeed the cause of users’ content-loading problems. We assessed our usage of OkHttp and checked if there were any upcoming plans to improve support. OkHttp did have an open ask for “Happy Eyeballs” #506, but no known plans to implement it. Out of due diligence, we also assessed other network libraries– but knew that moving off OkHttp would be a radical change, indeed. We read the RFC 8305, “Happy Eyeballs algorithm for dual-stack IPv4/IPv6”, and thought “wow, we don’t want to implement this ourselves.” And as we were studying that open OkHttp issue and thinking “If only they would…”

Your app would request data from the backend inside it's domain layer. As the other commenter mentioned, Retrofit is a commonly used library for interfacing with REST APIs, which is built on top of OkHttp (a more generic HTTP client).

OkHttp

It's like Netty or Wangle, but in Rust.

DotNetty is a port of Netty, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

As you are in i/o tasks, you can look at spring webflux / microprofile / quarkus. If you mature enough netty (https://netty.io/) based solution will be more effecient.

It's like Netty or Wangle, but in Rust.

In the ShardingSphere-Proxy front-end Netty decoding logic, when a data Packet of length 0xFFFFFF is encountered, the Payload part of multiple MySQL Packets is aggregated via CompositeByteBuf.

I've taken a look at Kryonet and Netty, but they seem to only be for client-to-server models (Correct me if I'm wrong).

One approach I do not think many consider is starting with the Netty, which is used by many frameworks. We ended up using this for our current product, and while this gives the ultimate flexibility in handling requests it also heightens the bar somewhat for the ones employing its use, as it just gives you the nuts and bolts and it is up to you to make it play nice for your use-cases. I had to write quite a few learning tests to grok it.

Since 4.1.50.Final, Netty’s Epoll has been available in Linux environments with aarch64 architecture. Under an aarch64 Linux environment, compared to Netty NIO API, performance can be greatly enhanced with the use of Netty Epoll API.