How to reorganize Service Management


Dan Kohn <dan@...>
 

https://landscape.cncf.io/grouping=landscape&landscape=service-management

The service management sub-category of the landscape is, IMHO, one of the most confusing.

It appears to be a grab bag of the following:

API GATEWAYS
3Scale
Ambassador
Kong
MuleSoft
Open Service Broker API

SERVICE MESH
Conduit
Envoy
Hystrix
Istio
Linkerd
Netflix Zuul
Turbine Labs
Vamp

LOAD BALANCER
Avi Networks
Backplane
F5
HAProxy
Heptio Contour
NGINX
Traefik

RPC
Apache Thrift
Avro
gRPC
Netflix Ribbon

OTHER
Open Policy Agent (OPA)
Reactive Interaction Gateway
Stolon

I would argue that Load Balancers are ultimately a subset of Service Mesh functionality, so those two categories should be combined. It's also debatable whether API gateways are a subset of Service Meshes.

RPC at least seems different to me, although those 4 might best be moved to the Streaming category: https://landscape.cncf.io/grouping=landscape&landscape=service-management,streaming

If we rename "Secure Images" to "Security and Policy", then Open Policy Agent (OPA) would probably belong there.

Your thoughts?
--
Dan Kohn <dan@...>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com


Lee Calcote
 

This one is a bit of a challenge. A few notes that may help clarify:

  • Turbine Labs is the vendor, Houston is their service mesh.
  • Yes, API Gateways are the closest in resemblance to Service Meshes, load-balancers next in line in terms of resemblance.
  • While OPA’s canonical use cases are security-oriented, as a policy engine it’s broadly capable of evaluating policies of many domains (non-security domains).
  • Hysterix should be booted from the service mesh category. It’s a client library, missing a control plane - one of the distinguishing characteristics of a service mesh.
    • While it might be painful to relabel, the same qualification applies to Envoy unto its own is falls into the Load Balancer category.

- Lee

On Jun 29, 2018, at 6:20 AM, Dan Kohn <dan@...> wrote:

https://landscape.cncf.io/grouping=landscape&landscape=service-management

The service management sub-category of the landscape is, IMHO, one of the most confusing.

It appears to be a grab bag of the following:

API GATEWAYS
3Scale
Ambassador
Kong
MuleSoft
Open Service Broker API

SERVICE MESH
Conduit
Envoy
Hystrix
Istio
Linkerd
Netflix Zuul
Turbine Labs
Vamp

LOAD BALANCER
Avi Networks
Backplane
F5
HAProxy
Heptio Contour
NGINX
Traefik

RPC
Apache Thrift
Avro
gRPC
Netflix Ribbon

OTHER
Open Policy Agent (OPA)
Reactive Interaction Gateway
Stolon

I would argue that Load Balancers are ultimately a subset of Service Mesh functionality, so those two categories should be combined. It's also debatable whether API gateways are a subset of Service Meshes.

RPC at least seems different to me, although those 4 might best be moved to the Streaming category: https://landscape.cncf.io/grouping=landscape&landscape=service-management,streaming

If we rename "Secure Images" to "Security and Policy", then Open Policy Agent (OPA) would probably belong there.

Your thoughts?
--
Dan Kohn <dan@...>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com


Chip Childers
 

On Fri, Jun 29, 2018 at 7:20 AM Dan Kohn <dan@...> wrote:
API GATEWAYS
3Scale
Ambassador
Kong
MuleSoft
Open Service Broker API

Open Service Broker API isn't an API gateway. I was going to suggest "service discovery", but it doesn't do runtime service discovery or even touch data path. Looking at the other categories it feels like "other" may be the best option. That, or "service catalog" becomes a category. 

--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815