OCI Service Mesh
Definition
Oracle's managed service mesh for microservices communication and security, ensuring reliable interactions and governance across services.
Use Cases
- Amazon: Standardizing service-to-service traffic controls and encryption for microservices running on containers. — Uses a service mesh approach (e.g., Envoy sidecars and centralized policy) to manage routing, retries, and mutual TLS between services without changing application code. (Improved consistency of security controls and traffic policies across services, with better visibility into service-to-service communication for troubleshooting.)
- Airbnb: Improving reliability and observability of microservice communication in a large distributed system. — Adopted a service mesh pattern using sidecar proxies to collect telemetry and apply network policies (such as timeouts and retries) at the infrastructure layer. (Better operational insight into inter-service calls and more resilient request handling through standardized traffic policies.)
Provider Equivalents
- AWS: AWS App Mesh
- OCI: OCI Service Mesh
Frequently Asked Questions
- What's the difference between OCI Service Mesh and Istio?
- OCI Service Mesh is a managed Oracle Cloud service that provides service-mesh capabilities (like mTLS, traffic policies, and telemetry) with Oracle handling much of the control-plane operation. Istio is an open-source service mesh you typically install and operate yourself (often on Kubernetes). With Istio you get more direct control and portability, but you also take on more operational responsibility.
- When should I use OCI Service Mesh?
- Use OCI Service Mesh when you run microservices (often on OKE/Kubernetes) and need consistent service-to-service security (mTLS), traffic management (routing, retries, timeouts), and observability (metrics/traces) without adding these features into every application. It’s most valuable when you have multiple services, multiple teams, or strict security/compliance requirements. If you only have a few services or simple communication patterns, a mesh may be unnecessary overhead.
- How much does OCI Service Mesh cost?
- Costs depend on OCI’s current pricing model and your usage. Even when the service control plane is low-cost or included, you should plan for indirect costs such as additional compute/memory for sidecar proxies (Envoy) on each pod, extra network egress (if applicable), and increased logging/metrics/tracing ingestion and storage. Always confirm pricing in the official OCI pricing page and estimate based on number of workloads, request volume, and observability retention.
Category: containers
Difficulty: advanced
Related Terms
See Also