4 ms·

Why wasn't this just open sourced?

_jal 6y ago
Ningx Plus isn't open-source, and this lives on top.
pseudosavant 6y ago
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.
- deleted 6y ago
  [deleted]
- deleted 6y ago
  [deleted]
lambdasquirrel 6y ago
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 6y ago
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.
- freedomben 6y ago
  Agreed, I don't see there being a big market for this. They are late to the party, cost more money, and are more closed source than the other alternatives. I don't know why anyone would choose this unless perhaps they already have Nginx Plus in place.
  - yacobucci 6y ago
    While built using nginx-plus as the sidecar the mesh is still free to use. There is no requirement to retain an nginx-plus subscription or to pay anything for the mesh.

_jal 6y ago

Ningx Plus isn't open-source, and this lives on top.

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.

deleted 6y ago
[deleted]
deleted 6y ago
[deleted]

lambdasquirrel 6y ago

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 6y ago

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.

freedomben 6y ago
Agreed, I don't see there being a big market for this. They are late to the party, cost more money, and are more closed source than the other alternatives. I don't know why anyone would choose this unless perhaps they already have Nginx Plus in place.
- yacobucci 6y ago
  While built using nginx-plus as the sidecar the mesh is still free to use. There is no requirement to retain an nginx-plus subscription or to pay anything for the mesh.