I am super excited to be presenting at the O’Reilly Software Architecture 2019, San Jose today. Please join me at 3 PM in Room 210 D/H to learn about building a scalable microservice architecture with Envoy, Kubernetes, and Istio.
Smart Pipes and Smart Endpoints with Service Mesh
Smart endpoints and Dumb Pipes has been one of the design principles for microservices during the last decade. Responsibility of the network is to just transfer messages between Source to Destination. Responsibility of microservices is to handle Business logic, transformation, validations, and process the messages.
Visualizing the Istio Service Mesh using Kiali
Kiali lets you monitor and visualize the Istio Service Mesh from within a single user interface. Kiali lets you view configurations, monitor traffic flow between services and analyze traces. It provides visibility into features likes service health, request routing, circuit breakers, request rate, traffic flow, error rate and more.
Chaos Testing your Microservices with Istio
Chaos Testing is a practice to intentionally introduce failures in your system to test the resiliency and recovery of your microservices architecture. The Mean Time to Recovery(MTTR) needs to be minimized in the current modern day architectures. Hence it is beneficial to validate different failure scenarios ahead of time and take necessary action items to stabilize the system and make it more resilient.
Retry Design Pattern with Istio
Retry Design Pattern states that you can retry a connection automatically which has failed earlier due to a network exception. Istio provides a transparent approach of handling application retires in case of such intermittent network errors.
Handling Service Timeouts using Istio
When you encounter latency with your service communication and you are not sure what the root cause is, it is a preferred approach to just not wait for the response. Implementing a timeout strategy between your service to service communication over the network is critical. Istio makes it pretty simple to implement this functionality within your service mesh.
Resilient Microservices with Istio Circuit Breaker
Circuit Breaker is a design pattern to create resilient microservices by limiting the impact of service failures and latencies. One of the primary goals of the Circuit Breaker pattern is to handle failures gracefully so that no cascading failures occur. In a Microservice landscape, failing fast is critical. Circuit Breaker does a great job in protecting the service from a heavy load.
Istio Circuit Breaker with Outlier Detection
Outlier Detection is an Istio Resiliency strategy to detect unusual host behavior and evict the unhealthy hosts from the set of load balanced healthy hosts inside a cluster. It automatically tracks the status of each individual host and checks metrics like consecutive errors and latency associated with service calls. If it finds outliers, it will automatically evict them.
Microservices Journey from Netflix OSS to Istio Service Mesh
Netflix OSS is a set of libraries & framework that Netflix open sourced to solve the issues with designing distributed systems at scale. In this blog post, you will understand the issues with the Netflix OSS libraries and why organizations are adapting the Sidecar Design pattern and Service Mesh technologies.
Istio Service Mesh Data Plane
The Istio Data Plane is primarily comprised of the Envoy proxies which are attached as dedicated sidecars to each application instance. Istio Data Plane intercepts all incoming(Ingress) and outgoing(Egress) network traffic. This and gives us the ability to apply all the features at this layer, without polluting the application code.