Solo is building a group of abstractions on service mesh to make them useful.
You see, the problem with cloud is that you lose the control of the networking. The abstraction of the network in AWS or Azure means that you have a few problems, incompativluty
But the real problem is that you lose control of the network, so you want to build a new one so that you get control of the traffic and insert L7 fucntionality. So using a service mesh overlay gives you back your visibility and control but also offers opportunities that aren’t possible with traditional networking.
Solo.io starts with Using Envoy as a an L7 Load Balancer – its called an API Gateway in cloud speak, but its a L7 proxy that does rate control, decryption etc. To make it specifically useful Solo Gloo is container aware and built with tools for knowing what’s in containers.
So far, it’s a good idea.
But you can build apps on the API gateways to automate various functions. examples apps are a inline debugger tool.
Super Gloo: the assumption is that you will have more than one service mesh because, well, Kubernetes doesn’t work so well at hosting many apps. Smaller K8S is currently the way forward instead of one big one.
Now operating istio service mesh is not a simple thing. SSL certificate management, enforced sidecar deployment,
Super Gloo aims to make this smoother. –
- SuperGloo takes charge of launching and managing key mesh functionalities, including encryption, telemetry, and tracing
- installation process of all supported service meshes, bypassing the often-complicated implementation-specific installation process.
- SuperGloo provides a f
- SuperGloo makes it easy to connect multiple service meshes across namespaces, across clusters, or across clouds, providing flat networking and policy.