QUIC Network Layer is Production Ready!

With the beta of 4D 20, we introduced you to our new network layer: The QUIC network layer. 

At that time, it was still in development and thus removed from the official release. Today, we’re thrilled to announce that the QUIC network layer is out of beta and officially ready for production!

After rigorous load testing and valuable feedback from early adopters, QUIC’s stability and performance have been validated—surpassing even ServerNet in key areas. Now that QUIC has reached feature parity with ServerNet in 4D 20 R5, it’s the perfect time to consider making the switch.

But first, let me tell you more about such great news.

When to switch to QUIC?

For new applications, the answer is simple: start using the QUIC network layer from day one. As future 4D versions will introduce even more functionality to QUIC, adopting it now ensures you’re prepared for what’s coming. By choosing QUIC, you’ll avoid the complexity of switching later on.

For existing applications currently running on ServerNet, check your network settings as described below and go ahead.

While ServerNet remains fully supported and there are no immediate plans to deprecate it, QUIC offers superior reliability and stability. It’s important to note that while QUIC won’t fix network outages, it excels in handling occasional packet loss or delays, where ServerNet might throw network errors. With future updates set to enhance QUIC even further, thinking ahead is essential.

That said, each network infrastructure is unique. So, before making the switch, test your setup with QUIC to ensure compatibility. We highly value your feedback during this phase, as it will help us further refine and optimize the QUIC network layer.

Key differences: QUIC vs. ServerNet

One important difference between ServerNet and QUIC is that ServerNet uses TCP while QUIC uses UDP. Most networks convey TCP and UDP the same way but many firewalls and switches block UDP as it is rarely used by applications. So if your 4D Server is not on the same subnet than your 4D Remotes (which is likely), we strongly recommend testing your applications with QUIC before planning a full switch. If you encounter connection issues, ensure that your routers or firewalls aren’t blocking UDP traffic.

A note for engined applications

Another thing to keep in mind: if you’re using engined applications, older clients may still need ServerNet to update to a version compatible with QUIC. Just keep your TCP ports open on the server until all clients have installed the QUIC-enabled version of your application.

I hope you’re as excited as we are about this new chapter in 4D networking! Stay tuned for even more updates and improvements in upcoming releases. As always, if you have any questions or need assistance, the 4D forum is just a click away.