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

Join cncf-reference-architecture@lists.cncf.io to automatically receive all group messages.