Solo.io Streamlines Service Mesh and Serverless Adoption for Enterprises in Google Cloud
Cloud-native architectures like microservices and serverless are ushering in a new wave of app infrastructure to handle these new apps — collections of small services that are distributed across many clusters. This decoupling and decomposition of monolithic applications raises new application ops questions like how to deploy, update, observe and secure your many services. To address these needs, Google Cloud has lead the industry in launching open-source projects like Istio for service mesh, Kubernetes for orchestration and Knative for serverless apps on Kubernetes. These projects help bring internal Google innovations out into the open and enable collaboration across the industry including end users, open-source enthusiasts, and commercial vendors.
Solo.io works on open-source projects and enterprise products that are designed to ease and accelerate the adoption of these new technologies in the enterprise alongside their existing environment. Our integrations to the Google Cloud ecosystem enable enterprises to deploy, secure and manage these new environments as part of their cloud migration, hybrid cloud and cloud native app strategies.
- Solo Gloo, the Modern API Gateway and Kubernetes Ingress
Solo Gloo is a next-generation API Gateway and Kubernetes Ingress built on top of Envoy Proxy which provides functionality like native Google Cloud Functions routing, powerful rate limiting and authentication/authorization options, request and response transformations, and a simplified domain-specific configuration model for configuring the routing and gateway capabilities. Gloo can be used to unify existing environments with cloud-native environments like GKE and Kubernetes from both the request-routing perspective as well as the observability and metric-collection perspective.
Solo Gloo can also simplify certain routing use cases. For example, in Knative, Gloo gives another option for routing when you may not already have or may not need a full service mesh. Because the Gloo control plane is designed to be easily extended to fit any environment, Gloo can easily be implemented as the Cluster Ingress gateway for Knative serving.
Gloo Community is available open source and Gloo Enterprise offers a 30 day trial. Gloo Enterprise offers additional features around management, observability, and security of APIs in a GUI admin console. Please see https://gloo.solo.io
2. Solo SuperGloo, the Service Mesh Orchestrator for Istio
Solo SuperGloo is an open-source project intended to help end users and operators successfully adopt and operate Istio service mesh. Istio is a powerful implementation of a service mesh and as our users begin to adopt it they look for guidance and tooling for integrating with their existing processes and procedures. SuperGloo codifies repeatable patterns for Day 2 operations of Istio including things like setting up the integration with your existing metric-collection engines, certificate authority/PKI, and progressive/continuous delivery pipelines.
Istio service mesh is at its most powerful when its able to span multiple clusters and operating environments. Correctly configuring this and operating this can be complex. SuperGloo helps simplify the management surface for a multi-cluster Istio service mesh by wiring up routing rules across clusters, distributing/rotating certificates by leveraging existing PKI, and piping your metric-collection systems to a single pane of glass whether that’s Google Cloud Stackdriver, DataDog, Prometheus or others.
Lastly, SuperGloo simplifies integrating and building on top of Istio with an SDK that handles the last-mile integrations with your existing networking and services infrastructure. Please checkout https://supergloo.solo.io for more.
3. Solo Squash, the Microservices Debugger for Kubernetes
Solo Squash is a distributed, remote, multi-language debugger for Kubernetes. Moving to a microservice-style architecture running in containers will force a change in tooling and processes. Solo Squash lessens this shift and enables developers to take their existing IDE and developer tooling with them when they move to a GKE or Kubernetes environment. Squash sets up the language-native debugger connections to your applications, regardless of what language they’re written with, so you can get step-by-step debugging in your IDE will running in Kubernetes. Solo Squash can also be used to debug service-to-service issues when running in a service mesh like Istio. Solo contributed a filter to Envoy Proxy which integrates with Squash to enable step-by-step debugging in Istio. See https://squash.solo.io for more!BACK TO BLOG