On the face of it that&#x27;s not very practical indeed, but that doesn&#x27;t mean it isn&#x27;t necessary in real-world scenarios. You don&#x27;t always control the applications behind your nginx reverse proxies and can&#x27;t always enforce correct behavior from them. They may come from a separate group which you can&#x27;t easily reach for political reasons or from some external vendor with its own roadmap.<p>This makes OpenResty a nice tool for operations&#x2F;security, because you have enough control to implement workarounds when required without having to wait for external entities. Some of you may cringe at the notion of implementing workarounds, but that&#x27;s standard practice in any corporate setting. The alternative is just worse and you learn to live with it by calling it &quot;application firewalls&quot;.<p>The other nice thing about OpenResty is the flexibility gained from separating scaling&#x2F;infrastructure logic from application logic. And this got even better in the last relase of the Lua module by allowing custom balancing logic in upstream blocks without having to hook into header_filter_by_lua or something like that to manipulate the URL to feed into proxy_pass.<p>Finally, there&#x27;s microservice (or microapplication) architectures, where your big application is really a bunch of smaller applications being glued together by logic in nginx (something like Edge Side Includes but nicer).