The core component used for traffic management in Istio is Pilot, which manages and configures all the Envoy proxy instances deployed in a particular Istio service mesh. Pilot lets you specify what rules you want to use to route traffic between Envoy proxies, which run as sidecars to each service in the mesh. Each service…
Back-end systems such as access control systems, telemetry capturing systems, quota enforcement systems, billing systems, and so on traditionally directly integrate with services, which creates a hard coupling, and it bakes in specific semantics and usage options. Istio Mixer provides a generic intermediation layer between app code and infrastructure back ends. Its design moves policy…
Istio can secure the communication between microservices without requiring app code changes. Security is provided by authenticating and encrypting communication paths within the cluster. This is becoming a common security and compliance requirement. Delegating communication security to Istio (as opposed to implementing TLS in each microservice), ensures that your app will be deployed with consistent…
The components deployed on the service mesh by default are not exposed outside the cluster. External access to individual services so far has been provided by creating an external load balancer or node port on each service. An ingress is a collection of rules that allow inbound connections to reach the cluster services. You can…
To effectively design and build apps for the cloud, you should understand the twelve factors: 1 Codebase: One codebase tracked in revision control, many deployments 2 Dependencies: Explicitly declare and isolate dependencies 3. Config: Store configuration in the environment 4 Backing services: Treat backing services as attached resources 5 Build, release, run: Strictly separate build and run stages 6 Processes: Execute…