Service-Mesh

 Youtube Guide :

https://www.youtube.com/watch?v=16fgzklcF7Y&t=716s   -- Best

https://www.youtube.com/watch?v=yxTR__Y0DnU -- Detail 

Istio Setting 

https://www.youtube.com/watch?v=voAyroDb6xk

A service mesh is an infrastructure layer used in microservices architectures to manage communication between services.

It handles things like:

  • Service-to-service communication
  • Traffic routing
  • Load balancing
  • Security (mTLS)
  • Monitoring and observability
  • Retry and failover policies

Instead of putting this logic inside each application, the service mesh manages it externally.

Popular Tools for service mesh

  1. Istio
    • Most widely adopted open-source service mesh
    • Uses Envoy proxies as sidecars
    • Strong traffic management, security (mTLS), observability, and policy controls
    • Common in enterprise Kubernetes deployments
    • Official site: Istio
  2. Linkerd
    • Lightweight and simpler than Istio
    • Focused on ease of use and low operational overhead
    • Good for teams wanting a minimalistic mesh
    • Official site: Linkerd
  3. Consul
    • Combines service discovery, configuration, and service mesh
    • Works across Kubernetes and VMs
    • Popular in hybrid/multi-cloud setups
    • Official site: Consul
  4. Kuma
    • Created by Kong
    • Supports Kubernetes and bare metal/VM workloads
    • Easier multi-zone management
    • Official site: Kuma
  5. Open Service Mesh
    • Lightweight CNCF mesh
    • Built around SMI (Service Mesh Interface)
    • Simpler feature set
    • Official site: Open Service Mesh
  6. AWS App Mesh
    • AWS-native managed service mesh
    • Integrates deeply with ECS, EKS, and EC2
    • Best for AWS-centric architectures
    • Official site: AWS App Mesh

Most commonly chosen today

  • Enterprise / feature-rich → Istio
  • Simplicity / low overhead → Linkerd
  • Hybrid infra → Consul

If you want, I can also compare:

  • Istio vs Linkerd
  • Best service mesh for Kubernetes
  • Service mesh interview questions
  • When not to use a service mesh
  • Architecture diagrams of service mesh systems


How it works

A service mesh usually uses:

  • Data Plane → lightweight proxies (sidecars like Envoy) alongside each service
  • Control Plane → manages configuration and policies

Popular Service Mesh Tools

  • Istio
  • Linkerd
  • Consul
  • Envoy
Common Features
  • Automatic encryption between services
  • Traffic splitting (blue/green or canary deployments)
  • Distributed tracing
  • Metrics collection
  • Fault injection/testing
  • Access policies

Example

Without service mesh:

Service A → custom retry logic → Service B

With service mesh:

Service A → sidecar proxy → sidecar proxy → Service B

The proxies handle retries, TLS, logging, and routing automatically.

How it works

A service mesh usually uses:

  • Data Plane → lightweight proxies (sidecars like Envoy) alongside each service
  • Control Plane → manages configuration and policies



Istio Setup



s

Comments

Post a Comment

Popular posts from this blog

Azure Migrate

Image
 Azure Site Recovery an earlier tool for migration: Thought purpose built for Disaster Recovery ASR: Azure Site Recovery Yes — Azure Site Recovery (ASR) is commonly used as a migration tool , even though its primary purpose is disaster recovery. How ASR Is Used for Migration Organizations use ASR to perform: Lift-and-shift migrations VMware to Azure migrations Hyper-V to Azure migrations Physical server to Azure migrations ASR replicates workloads continuously from on-premises infrastructure to Azure. During the final cutover, the replicated VM is started in Azure with minimal downtime. Migration Workflow Using ASR Typical Flow Discover on-prem servers Enable replication Continuous data synchronization Test failover (optional) Planned failover/cutover Azure VM becomes production workload This approach minimizes: Downtime Data loss Manual rebuild effort Why ASR Is Popular for Migration ASR vs Azure Migrate Real-World Use Case Example: Company has 200 VMware VMs on-premises. The...
Read more

Azure -- All Networking Components

   1. Virtual Network (VNet) 📌 One-paragraph explanation A Virtual Network (VNet) is the core private networking space in Azure where all cloud resources communicate securely. It is used to isolate workloads, control IP ranges, and create a private environment similar to a traditional data center network but fully software-defined in the cloud. 🔍 Details Where used: Hosting VMs, AKS clusters, databases, internal services Connected services: VM, Load Balancer, Application Gateway, Azure Firewall, Private Endpoint Dependencies: None (foundation component) Purpose in architecture: Acts as the main “network boundary” for all resources 🧩 2. Subnet 📌 One-paragraph explanation A subnet is used to divide a VNet into smaller logical networks so that different layers of an application (web, app, database) can be separated and controlled independently for security and traffic management. 🔍 Details Where used: Tiered architectures (web/app/db layers), microse...
Read more

All Kuberneters - Components

  Kubernetes Core Resources Explained 1. Pods What It Is A Pod is the smallest deployable unit in Kubernetes. It contains one or more containers that share: Network Storage Lifecycle Used For Running application containers Grouping tightly coupled containers together Example A web application container running inside a pod. 2. Deployments What It Is A Deployment manages Pods and ReplicaSets. Used For Rolling updates Application version upgrades Scaling applications Self-healing applications Example Deploying 3 replicas of an NGINX application. 3. ReplicaSets What It Is A ReplicaSet ensures a specified number of pod replicas are always running. Used For High availability Maintaining desired pod count Example Keeping 5 backend pods running at all times. 4. DaemonSets What It Is A DaemonSet ensures one pod runs on every node (or selected nodes). Used For Monitoring agents Log collectors Security agents Example Running Fluentd or Prometheus Node Exporter on all nodes. 5. StatefulSets W...
Read more