ServiceMesh

A dedicated infrastructure layer (Istio, Linkerd) for service-to-service traffic — mTLS, retries, observability, without app code changes.

Why we need this / what value this brings

Handles service-to-service concerns (mTLS, retries, observability) uniformly across many services without repeating the logic in each one.

When to use this

Only once there are enough internal services that these cross-cutting concerns are genuinely duplicated pain — significant added operational complexity otherwise.

How to use or implement this

Not relevant to Localz's current architecture; revisit only alongside a genuine microservices migration.

Research questions

• Only relevant once Localz has enough services that mesh-level concerns (mTLS between them) matter — currently far future.

---

Empty folder — drop notes, links, and findings here as you research.