Kubernetes is an open source container-orchestration system for automating deployments, scaling and management of containerized applications. In this tutorial, you will learn how to get started with Microservices on Kubernetes. I will cover the below topics in details — How… Read More ›
Transforming your existing legacy monolithic application into cloud native microservice is a nice end goal to have, but the journey is challenging and needs to be well architected and planned. In this article, we will discuss about a design pattern called as ‘Strangler Pattern’ which can assist you in this journey.
Handling database changes in your journey from Monolith to Microservice is challenging. In this article, we will understand the problems with Monolithic Database Design and how you can handle your data in a microservice architecture.
In this blog post, I will show you how to troubleshoot an error message displayed while connecting to AWS Aurora indicating that you cannot execute the statement with the read only option.
I am excited to be presenting at the Atlanta Code Camp this weekend. This will be my 3rd year speaking at this awesome conference. I am looking forward to meeting a lot of folks from the Tech community and having a good time.
In this blog post, I will show you how to troubleshoot and resolve connectivity issues with Aurora MySQL RDS Instance.
In this blog post, I will show you how to debug and troubleshoot issues with your AWS DMS Tasks during the migration of large tables from On-Premise to Cloud.
SQL Saturday Birmingham 2019 was held at the Brock School of Business – Cooney Hall – Samford University on 27th July. The event was a huge success. We had close to 200 folks registered to the event and had a final turnaround of around 150.
Just back from SQL Saturday Pensacola 2019, and I would say it was a fun event like always. This was my 3rd consecutive year speaking at the event and I really look forward to this event every year because the Organizing Team including Ed Watson, Karla Landrum, and others does a great job. Pensacola is also the summer holiday gateway for me so I do enjoy this trip.
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 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.
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 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 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.
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.
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.
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.
Prometheus is an open source metrics-based monitoring and alerting system. In 2016 the Prometheus project became the second member of the Cloud Native Computing Foundation, after Kubernetes. It has a powerful query language(PromQL) with a multidimensional data model suited to store time series data.
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.
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.
Istio is a very popular Service Mesh Framework which uses Lyft’s Envoy as the sidecar proxy. Service Mesh gives you the freedom of not having to worry about the service to service communication as part of your application code. Instead of bloating your microservice with similar functionalities, you can let the Service Mesh handle that complexity for you.
The Eight Fallacies of Distributed Computing are a set of assumptions that developers make while designing Distributed Systems which might backfire and cause additional work and system redesign in the long run. Designing Distributed Systems is challenging and being aware of these eight fallacies will help you in architecting your systems better.
Yesterday Istio 1.1 was released which primary focuses on addressing the performance and scalability issues which organizations bumped into running large clusters in Production environment. There are a number of improvements to both the Data Plane & Control Plane to make it more efficient and also significant improvements to the overall product.