Here are five tools to level up your Kubernetes journey; no matter if you are just getting started or deep in the K8s, read on to see why I picked them. 🦮

In part 1 I proposed a simple modification to Google’s Multi-Window Multi-Burn Rate alerting setup and I showed how this modification addresses the cases of varying-traffic services and typical latency SLOs.

One of the great chapters of Google’s Site Reliability Engineering (SRE) second book is chapter 5 — Alerting on SLOs (Service Level Objectives). This chapter takes you on a comprehensive journey through several setups of alerts on SLOs, starting with the simplest non-optimized one and by iterating through several setups reach the ultimate one, which is optimized w.r.t to the main four alerting attributes: recall, precision, detection time and reset time.

We talk and hear a lot about Regression everywhere we go. So let us skip that. In this article, we shall assume that we are masters of Regression and we have already completed building a Linear Regression Model on a given dataset.

Developers use GitHub to store and manage their codes, as well as track and control changes to the codes they create.

With the advent of handheld devices, there is a paradigm shift in usage and demand for Enterprise Software. On one hand, most of the companies have large complex and monolithic systems in place which take care of huge and complex business scenarios, rules, and computations, and on the other hand, there is a need to provide an easy way to access information to the customer on their Mobile devices.

In this article I will explain Event Sourcing Pattern which is a widely used pattern for microservice artitechtured applications nowadays. In otherside I think it will change your look to development and give you a new vision. I will endeavor to explain this topic to you in two steps.

Microservice Architecture is gaining lot of popularity and wider adoption within the community.