Grey Matter Fabric powers the zero-trust hybrid service mesh, and consists of the Edge, Control, Security, and Sidecar. Use Fabric to connect services built with any language, framework, or runtime environment.
Get a refresher on how Fabric fits into Grey Matter's architecture.
The Grey Matter Edge handles north/south traffic flowing through the mesh. You can configure multiple edge nodes based on throughput or regulatory requirements, requiring segmented routing or security policy rules. These include:
Traffic flow management in and out of the hybrid mesh
Hybrid cloud jump points
Load balancing and protocol control
Edge OAuth security
Grey Matter Control is a microservice that performs the following functions within Fabric:
Automatic discovery throughout your hybrid mesh
Templated static or dynamic sidecar configuration
Telemetry and observable collection and aggregation
Neural net brain
API for advanced control
Learn more about Grey Matter Control here.
Fabric offers the following security features:
Verifies that tokens presented by the invoking service are trusted for such operations
Performs operations on behalf of a trusted third party within the Hybrid Mesh
The Grey Matter Sidecar is a deployment strategy that uses the Grey Matter Proxy. Add Grey Matter to your microservices by deploying a sidecar proxy throughout your environment. This sidecar intercepts all network communication between microservices.
The Grey Matter Sidecar offers the following capabilities:
Multiple protocol support
Observable events for all traffic and content streams
Certified, Tested, Production-Ready Sidecars
Native support for gRPC, HTTP/1, HTTP/2, and TCP
Once you've deployed the Grey Matter Sidecar, you can configure and manage Grey Matter with its control plane functionality:
Automatic load balancing for HTTP, gRPC, WebSocket, and TCP traffic
Fine-grained control of traffic behavior with rich routing rules, retries, failovers, and fault injection
A policy layer and configuration API supporting access controls, rate limits and quotas
Automatic metrics, logs, and traces for all traffic within a cluster, including cluster ingress and egress
Secure service-to-service communication in a cluster with strong identity-based authentication and authorization