HPA, when triggered, is going to scale out a specific deployment, meaning, increase the number of running instances of an application to handle a particular workload. In a previous post, “Understanding Kubernetes HPA with KEDA and RabbitMQ” we have learned how to implement a simple, scalable application.

What if our scaled applications need dependencies stored somewhere a little far from our cluster?? things will get more interesting and exciting here!

This article will show us how to design a Kubernetes job with all necessary objects that will fetch dependencies from Azure Storage Account and feed them to our applications before…

Real-world Kubernetes stateless applications are designed carefully to separate code from other components like databases or queues, which makes it easier to scale up or down the code component (or so-called the stateless application). There are different scenarios where the application needed to be scaled and that depends on the nature of our business requirements. One scenario can be an application that processes messages in the RabbitMQ server outside the Kubernetes cluster, the queue may have thousands or millions of messages that must be processed as quickly as possible via the application, thus one instance of the application will not…

Tamer Abdulghani

Software Engineer @ Capgemini, CKAD, Cloud Native, Architecture, MCSD, Azure, Domain Driven Design

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store