DField SolutionsMérnöki stúdió · Budapest
Loading · Töltődik
Skip to content
Back to glossaryTERM

Service mesh

Related service Websites, web apps & online shops

DEFINITION

A service mesh is an infrastructure layer (Istio, Linkerd, Cilium Service Mesh, Consul) that intercepts every network call between microservices: service-to-service mTLS, retry, timeout, circuit breaker, traffic split (canary, blue-green), observability, and policy enforcement. The logic moves out of your application into a sidecar proxy (Envoy) or an eBPF layer, so it is language-agnostic. It sounds compelling, and vendors love selling it. In reality: if you have fewer than 8 services, if everything is one language (say gRPC), and Kubernetes is a single familiar cluster, then 80 percent of what a mesh would do can be solved with a good library (gRPC retry, OpenTelemetry, cert-manager) plus Kubernetes NetworkPolicy. You actually need a mesh when many languages plus many teams plus strict zero-trust (PCI, fed) plus multi-cluster topology combine. Otherwise the operational cost (control plane, sidecar memory, debugging) eats the benefit.

RELATED TERMS06
  • Answer Engine Optimization (AEO)→

    We shape content so AI answer engines (ChatGPT, Perplexity, Google AI overviews) cite YOU: clear claims, structure, sources, schema. The successor discipline to classic SEO in 2026.

  • Zero-Click Search→

    Searches resolved right on the results page (AI overview, snippet) with no click to any site. Rising fast: you win by being the cited source, not just by ranking.

  • Featured Snippet→

    The boxed answer Google lifts to the top ("position zero"). Win it with a crisp, directly-phrased answer placed right under a question heading.

  • People Also Ask→

    Google's expanding box of related questions. Each one is a content opportunity: answer them explicitly to capture the box and the long-tail traffic.

  • Crawl Budget→

    How many pages a search engine will crawl on your site per visit. It matters for large sites: waste it on junk URLs and your important pages get crawled late.

  • Canonical URL→

    The <link rel="canonical"> that tells search engines which URL is the master when duplicates or params exist. Prevents ranking signals from being diluted across near-identical pages.

MENTIONED IN THE BLOG05