---
description: Learn about the major components in the Grey Matter ecosystem.
---

# Core Components

![](https://2512473607-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsNFVozLgvw3NDMzxBg%2F-LyUgM-NxRBA2Uxg0muk%2F-LyUgU4hcVvrHpM-XR3S%2FCore%20requirements%404x.png?alt=media\&token=c307da43-e03b-4b6e-89d9-137102da40bd)

{% hint style="success" %}
Use the concepts in this document alongside our [Guides](../../guides) when deploying Grey Matter in production.
{% endhint %}

## Overview of Grey Matter's Functionality

Grey Matter is composed of **Fabric, Data,** and **Sense**. Internal to each component is a series of microservices that offers several core features. Each feature simplifies technical challenges associated with service management, such as:

* Announcement
* Discovery
* Instrumentation
* Logging
* Tracing
* Troubleshooting
* Encryption
* Access control
* Network/micro/data-segmentation

## Workload Distribution

The following diagram shows the workload distribution between Grey Matter's core components.

![](https://2512473607-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsNFVozLgvw3NDMzxBg%2F-Lvf59VQrjr1aZoDOx7N%2F-LvfBwht_niyoMafg_Ih%2FGrey%20Matter%20Layer%20Cake%408x-squashed.png?alt=media\&token=8e70dd9a-6237-4ac9-a8e3-4826ea0cce07)

## Grey Matter Fabric

Fabric powers the zero-trust hybrid service mesh, which consists of the [**Edge**](#edge), [**Control**](#control), [**Security**](#security), and [**Sidecar**](#sidecar). You can use Fabric to connect services regardless of language, framework, or runtime environment.

{% hint style="info" %}
**How does Fabric work?**

1. Fabric's sidecar proxies run alongside each microservice.
2. Each proxy manages scaling, access control, and intercommunication. _\*\*_
3. The proxy layer orchestrates communications between microservices operating in the mesh to provide reliability, visibility, and security.
{% endhint %}

Secure network fabrics provide bridge points, observability, routing, policy assertion, and more between on-premise, multi-cloud, and multi-PaaS capabilities. Fabric offers workload distribution and management within a hybrid environment.

### Support for Multiple Runtime Environments

Grey Matter supports multiple runtime environments with multi-mesh bridges as shown below. These environments include:

* Multiple cloud providers (i.e. AWS and Azure)
* Container management solutions (i.e., K8s, OpenShift and ECS)
* On-premise infrastructure

![The Grey Matter Hybrid Platform](https://2512473607-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsNFVozLgvw3NDMzxBg%2F-Lvf59VQrjr1aZoDOx7N%2F-LvfC4CHWxDB9FjtfaTB%2FGrey%20Matter%20Hybrid%20Platform%20diagram%408x-squashed.png?alt=media\&token=2e7463e0-3096-4531-9f47-def075ecce02)

{% hint style="success" %}
Grey Matter gives you the flexibility to deploy the mesh to suit your environment. Learn more about our [deployment options](hybrid-and-multi-mesh-deployments) here.
{% endhint %}

### OSI Model Layers

Fabric operates at [OSI model](https://en.wikipedia.org/wiki/OSI_model) layers 3 (network), 4 (transport), and 7 (application) simultaneously. Providing a powerful, performant, and unified platform to run, manage, connect, and perform distributed workloads across a hybrid architecture.

**Layer 3** operates at the TCP level. Responsible for transferring data “packets” from one host to another using IP addresses, TCP ports, etc., determining which route is the most suitable from source to its destination. At this level, network-segmentation is able to be performed using ABAC, RBAC, and NGAC policies set within each sidecar. More details can be found in the [Security Model](https://app.gitbook.com/@deciphernow/s/grey-matter-outline/introduction/internals/security-models) section.

**Layer 4** coordinates data transfer between clients and hosts. Adding load balancing, rate limiting, discovery, health checks, observability, and more built on top of TCP/IP. Layer 3 and 4 alone live within the TCP/IP space and are unable to make routing decisions based on different URLs to backend systems or services. This is where layer 7 comes into the architecture.

**Layer 7** sits at the top of the OSI model, interacting directly with services and applications responsible for presenting data to users. HTTP requests and responses accessing services, webpages, images, data, etc. are layer 7 actions.

{% hint style="success" %}
Grey Matter Fabric offers a fast, simple, and elegant model to build modern architecture while bridging legacy applications.
{% endhint %}

The following graphic shows Fabric's basic capabilities--access, routing decisions, rate limits, health checks, discoverability, observability, proxying, network and micro-segmentation--and how they leverage all features found within each of the OSI layers described above.

![Grey Matter Fabric simultaneously functioning within layers 3, 4, and 7](https://2512473607-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsNFVozLgvw3NDMzxBg%2F-Lvf59VQrjr1aZoDOx7N%2F-LvfCDq-DDZ9OgK6uYbv%2FGrey%20Matter%20Fabric%20simultaneously%20functioning%20within%20layers%203%2C%204%2C%20and%207%408x-squashed.png?alt=media\&token=9551244a-e404-4cad-af92-8c5680fc66a1)

### Edge

**Grey Matter Edge** handles [north/south traffic](hybrid-and-multi-mesh-deployments) flowing through the mesh. Multiple edge nodes can be configured depending on throughput or regulatory requirements requiring segmented routing or security policy rules.

* Traffic flow management in and out of the hybrid mesh.
* Hybrid cloud jump points.
* Load balancing and protocol control.
* Edge OAuth security.

{% hint style="info" %}
**Note:** the **Grey Matter Edge** and **Grey Matter Sidecar** are _**the same binary**_ configured differently based on north/south and east/west access patterns.
{% endhint %}

### Control

* 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.

![Simple deployment architecture.](https://2512473607-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsNFVozLgvw3NDMzxBg%2F-Lvf59VQrjr1aZoDOx7N%2F-LvfBd2evPHlXA2TzrpP%2FSimple%20Deployment%20Architecture%408x-squashed.png?alt=media\&token=ce74493c-ddf7-4b2e-9d07-6f7aba1cf17c)

### Security

Grey Matter 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.

### Sidecar

Add Grey Matter to services 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.
* Filter SDK.
* Certified, Tested, Production-Ready Sidecars.
* Native support for gRPC, HTTP/1, HTTP/2, and TCP.

{% hint style="info" %}
**gRPC Protocol Basics**

* gRPC is an RPC protocol implemented on top of HTTP/2
* HTTP/2 is a Layer 7 (Application layer) protocol that runs on top of a TCP (Layer 4 - Transport layer) protocol
* TCP runs on top of IP (Layer 3 - Network layer) protocol
{% endhint %}

Once you've deployed the Grey Matter Sidecar, you can configure and manage Grey Matter with its control plane functionality.

#### Grey Matter Control Plane Functionality

* Automatic load balancing for HTTP, gRPC, WebSocket, and TCP traffic
* Fine-grained control of traffic behavior with rich routing rules, retries, failover, 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

**Example**

The following diagram shows how the Grey Matter Sidecar would operate in a North/South traffic pattern.

![North-South Traffic Pattern.](https://2512473607-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsNFVozLgvw3NDMzxBg%2F-Lvf59VQrjr1aZoDOx7N%2F-LvfBkyIc4hEjaV3cC5B%2FNorth-South%20Pattern%408x-squashed.png?alt=media\&token=fcb98204-44f1-4cc8-a658-ee7decbe06f0)

## Grey Matter Data

**Grey Matter Data** is an API that enables secure and flexible access control for your microservices. Data consists of Grey Matter Data and JWT server, and includes an API Explorer to help you manage the API.

![Grey Matter Data's API Explorer simplifies the user experience.](https://2512473607-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LsNFVozLgvw3NDMzxBg%2F-LtVPjns7o1_3Y2AaNZm%2F-LtVS3DoQPe5PX16qJf_%2FGrey%20Matter%20Data%20%E2%80%93%20API%20Explorer.png?alt=media\&token=880be789-385d-4469-9b53-6e1c3f2febdf)

## Grey Matter Sense

**Grey Matter Sense** consists of four primary components: [**Intelligence 360**](..#intelligence-360), [**SLO**](..#slo), [**Business Impact**](..#business-impact) and [**Catalog**](..#catalog).

## Intelligence 360

**Intelligence 360** is our user dashboard that paints a high-level picture of the service mesh. Intelligence 360 includes the following features:

* Mesh Overview
  * Running state of all services
  * Search, sort and filter options
* Historical metrics per service
  * SLA warnings/violations (powered by [**SLO**](..#slo))
  * Resource usage
  * Request traffic
  * Route usage
  * Route-level metrics
* Real-time metrics per service instance
  * Service instance drill down
  * Metrics explorer
* Service configuration
  * Business impact
  * SLO
  * Sidecar settings

## SLO

**Grey Matter Service Level Objectives (SLOs)** allows users to manage objectives towards service-level agreements. These objectives can be internal to business operations or made between a company and its customers. They are generic and are valuable in more than one use case.

{% hint style="success" %}
**Key Definition**

**SLOs** are simply service performance objectives associated with metrics collected by the [**Grey Matter Sidecar**](..#sidecar), such as memory usage, request traffic (request rate, error rate, and latency).
{% endhint %}

SLOs combine with Intelligence 360 time-series charts to visualize warning and violation thresholds for targeted performance analysis. These objectives are used even further to train Sense AI for service scaling recommendations.

## Business Impact

**Business Impact** allows users to set metadata on services with the goal of associating how critical a service is towards the operations of a company, mission, or customer. Business Impact provides a list of values (Critical, High, Medium, Low) that correlates each service's business impact. Sense lets users of Intelligence 360 configure these values themselves, which can be used to filter and search via the mesh overview.

## Catalog

[**Grey Matter Catalog**](https://github.com/DecipherNow/gm-gitbook-sync/tree/1f07fcb61c80f05e1a6026915435977468694b44/introduction/internals/catalog.md) acts as an interface between the data plane (network of sidecars) of the service mesh and Intelligence 360. Catalog provides a user-focused representation of the mesh.

Learn how to [use the Catalog](../../usage/sense/catalog) here.

## Questions?

{% hint style="success" %}
**Want to learn more about Grey Matter Sense?** Contact us at [info@greymatter.io](mailto:info@greymatter.io) to discuss your use case.
{% endhint %}

## Need Help?

{% hint style="success" %}
Create an account at [Grey Matter Support](https://support.greymatter.io/support/home) to reach our team.
{% endhint %}
