[HN Gopher] The Future of Nginx: Getting Back to Our Open Source...
       ___________________________________________________________________
        
       The Future of Nginx: Getting Back to Our Open Source Roots
        
       Author : soheilpro
       Score  : 16 points
       Date   : 2022-08-23 22:00 UTC (59 minutes ago)
        
 (HTM) web link (www.nginx.com)
 (TXT) w3m dump (www.nginx.com)
        
       | kungfufrog wrote:
       | To me it totally sounds like 'all those features (some bizarrely
       | so) we locked behind a commercial license to extract money from
       | you' has resulted in people looking for alternatives as soon as
       | the use case exceeded the capabilities of the open source
       | version. Kubernetes and the ecosystem is eating their lunch for
       | more complex service mesh deployment scenarios where nginx is
       | basically an interchangeable dumb proxy, and doing it with
       | generally new and free open source products, so here, have some
       | more stuff we've kept gated behind an expensive
       | license/subscription so we can stay relevant.
       | 
       | I don't say this to be ungrateful about what nginx has provided
       | for free, it's great, thank you. But the post also feels like a
       | cynical take about what the value of open source truly is.
        
         | miohtama wrote:
         | My web server path has been Apache -> (Varnish) -> Nginx ->
         | Caddy. This outside programming language specific servers like
         | Waitress or Express.js.
         | 
         | I love the fact that Caddy is a single binary I can run for
         | simple use cases without configuration file. Plus the built-in
         | Let's Encrypt support. Nginx is definitely on defence here
         | unless you need "web scale" servers.
        
           | kungfufrog wrote:
           | Also a huge fan of Caddy!!!
           | 
           | Such a smart design and incredibly useful piece of software!
        
         | kungfufrog wrote:
         | Also, if you need further evidence of this, look at the MARA
         | diagram. It basically spells it out. There's 2 products in that
         | stack that are branded: nginx and Kubernetes, the rest is
         | noise, with nginx positioned as the only component for traffic
         | ingress. Also if that napkin scribbling constitutes an
         | "architecture"...
        
       ___________________________________________________________________
       (page generated 2022-08-23 23:00 UTC)