CloudTweaks | Service Mesh Impact

What is a Service Mesh?

A service mesh is a configurable infrastructure layer for microservice-based applications that makes communication between service instances flexible, reliable and fast. It provides features such as traffic management, service discovery, load balancing and security. It typically uses a sidecar proxy for each service instance to handle communication between service instances and to provide these functions. Examples of service masks include Istio, Linkerd, and Envoy.

White Cloud Tech

How a service network works

A service mesh is typically implemented as a distributed set of proxies that are deployed alongside application code and is responsible for traffic management, service discovery, load balancing, and security.

The data plane of a service network is the set of proxies installed with the application code. These proxies are responsible for handling the actual traffic between service instances, and they use the configuration provided by the control plane to make routing decisions.

The control plane of a service network is the management component responsible for configuring and maintaining the proxies in the data plane. The control plane communicates with the proxies in the data plane to propagate configuration changes and collect telemetry data. Here are the control aircraft’s main areas of responsibility:

  • Service register: The control plane maintains a list (registry) of available services and endpoints and makes it available to proxies. It requires querying an underlying infrastructure planning system, such as Kubernetes, to get a list of the available services.
  • Sidecar proxy configuration: The control plane stores policies and mesh-wide configurations that proxies use to perform their functions correctly.

Here are the main functions performed by service mesh proxies:

  • Service Discovery: An instance that needs to interact with another service must find (discover) a healthy and available instance, typically by performing a DNS lookup. Container orchestration frameworks usually maintain a list of instances available to receive requests and provide the interface for DNS queries.
  • Load Balancing: Orchestration frameworks typically provide Layer 4 load balancing, while a service mesh can implement more sophisticated Layer 7 load balancing that uses advanced algorithms and powerful traffic management.
  • Approval and authorization: A service network can approve and authenticate the various requests made from within the application and externally and send validated requests to instances.
  • Observability: Most service mesh frameworks provide insight into the health and behavior of services. The control plane collects and aggregates telemetry data from component interactions to assess service health using factors such as distributed tracing, access logs, traffic, and latency.

What is FinOps?

FinOps (short for “Financial Operations”) is a set of practices, principles and tools designed to optimize and manage the cost, usage and performance of cloud infrastructure and services. It’s a cross-functional approach that brings together the traditional silos of finance, operations and development teams to better understand, manage and optimize the costs associated with cloud infrastructure and services.

The main goal of FinOps is to enable organizations to use cloud services in a way that is economically efficient, operationally sound and aligned with business objectives. This is achieved by implementing a set of best practices that help organizations track, optimize and predict their cloud costs, as well as automate the processes of provisioning, scaling and retirement of cloud resources.

FinOps practices include cost management, utilization optimization, forecasting, budgeting and chargebacks. FinOps also includes the use of various tools such as cost optimization, cost visualization and entitlement sizing tools to help organizations better manage their cloud costs.

How Service Mesh affects your cloud costs

The service grid has the potential to affect cloud costs in several ways. Here are some of the main pros and cons:


  • Improved resource utilization: The service grid provides features such as load balancing, service discovery, and traffic management that can help improve the utilization of cloud resources. This can result in cost savings by reducing the need to overprovision resources.
  • Better visibility and control: The service mesh provides detailed observability and control over the communication between service instances, which can help identify and resolve issues that can affect the performance and cost of cloud services.
  • Reduced security and compliance costs: The service network can provide security and compliance features, such as authentication and encryption, that can help reduce the need for additional security and compliance services.


  • Additional resource requirements: Service mesh introduces an additional layer of infrastructure and requires additional resources to function, such as sidecar proxies and a control plane. These resources can increase the overall cost of running cloud services.
  • Complexity: The service network can add complexity to the architecture and management of cloud services, which can increase the cost of operating and maintaining cloud services.
  • Lack of standardization: Service mesh is relatively new and there is a lack of standardization among different service mesh implementations, which can make it difficult to compare costs and switch between different service meshes.


In conclusion, service masks are a powerful tool to improve the communication and management of microservices in cloud environments. They provide features such as traffic management, service discovery, load balancing and security that can help improve the utilization of cloud resources and provide better visibility and control over cloud services.

However, service mesh also comes with additional resource requirements and complexity that can affect cloud costs. As such, implementing a service network requires careful consideration of the organization’s specific needs and the costs and benefits of doing so.

From a FinOps perspective, service masks can be a valuable tool for managing and optimizing cloud costs, but organizations should be aware of the additional resource requirements and complexity associated with these solutions.

By Gilad David Maayan


Leave a Reply

Your email address will not be published. Required fields are marked *