[HN Gopher] Nginx Service Mesh
       ___________________________________________________________________
        
       Nginx Service Mesh
        
       Author : bhaavan
       Score  : 25 points
       Date   : 2020-10-21 09:55 UTC (1 days ago)
        
 (HTM) web link (www.nginx.com)
 (TXT) w3m dump (www.nginx.com)
        
       | 02020202 wrote:
       | yet another brick into the cloud wall that removes the programmer
       | away from the code and hardware. oh how i hate cloud. just more
       | and more tech and shite.
        
       | stuff4ben wrote:
       | So this is to compete with Envoy? If Nginx can solve the
       | documentation and the "why the hell do I need this" problem, it
       | might be worth looking into.
        
       | okokok___ wrote:
       | Why wasn't this just open sourced?
        
         | pseudosavant wrote:
         | I'm pretty sure Nginx isn't interested in open-sourcing any
         | more code than they have to at this point. Most of their
         | development seems to be closed-source these days.
        
         | lambdasquirrel wrote:
         | It's too bad they didn't. Otherwise, we could run istio and
         | nginx-service-mesh side by side, and use dns to traffic-split
         | between them. And then it would be network traffic splits all
         | the way down, into retries and fail-overs in the app logic.
        
         | oneplane wrote:
         | Because of F5 and because of nginx-plus. They keep trying to
         | push the closed stuff, but that's not what people want. We
         | don't mind paying, but we do mind not having public sources.
         | 
         | Ironically, this is practically stillborn unless people are
         | already nginx-plus customers, as everyone else is using Istio
         | (with Envoy) or bare Envoy or Traefik or Consul Connect or
         | HAProxy or Linkerd or any of the other billion options out
         | there. And when you are an nginx-plus customer you are unlikely
         | to have a model where a mesh fits in. For a mesh to make sense
         | you need to have more than just a need for service discovery;
         | i.e. you have to have dynamic locations and counts of sources
         | and destinations (or as people say: Kubernetes with automatic
         | rollout waves and lots of changes and deploys all day long).
         | The scenario where you have 'all the cool toys' but also 'need'
         | nginx-plus (and NSM) seems unlikely to me.
        
         | _jal wrote:
         | Ningx Plus isn't open-source, and this lives on top.
        
       ___________________________________________________________________
       (page generated 2020-10-22 23:00 UTC)