Heroku, with its 12-factor application model, has changed the way we think about building, deploying, and hosting web applications.
The rise of containers, phoenix servers and continuous delivery has seen a move away from the usual approach to deploying web applications. Traditionally we have built an artifact and then installed that artifact into an application server. The result was long feedback loops for changes, increased build times and the not insignificant overhead of managing these application servers in production. Many of them are a pain to automate too. Most teams we work with favor bundling an embedded http server within your web application. There are plenty of options available: Jetty, SimpleWeb, Webbit and Owin Self-Host amongst others. Easier automation, easier deployment and a reduction in the amount of infrastructure you have to manage lead us to recommend embedded servers over application servers for future projects.
Cloud Native Apps
https://dev.to/syncsynchalt/safe-http3-experimentation-with-caddy-447f
https://requestmetrics.com/web-performance/http3-is-fast
