#MASSTRANSIT VS DAPR SERIES#

Part 4 will conclude the series with another example to demonstrate how KEDA and Virtual Kubelet can be combined to deliver scalability.Part 2 will showcase KEDA auto-scaling in action with a practical example.Part 1 (this post) will cover basic KEDA concepts.Here is a breakdown of the blog posts in this series:

Kubernetes Event-driven Autoscaling (KEDA), which is another open source component that can be added into any Kubernetes cluster to drive the scaling of any container based on the workload.Virtual Kubelet, an open source Kubernetes kubelet implementation that allows Kubernetes nodes to be backed by providers, including serverless cloud container platforms.This blog series will cover open source components that can be used on top of existing Kubernetes primitives to help scale Kubernetes clusters, as well as applications. This can also be done manually, but you can use a cluster autoscaler that will scale your cluster up and down in an automated fashion. You might also need to scale out the underlying Kubernetes nodes, such as virtual machines, bare metal instances, etc. You can do it manually, but the Horizontal Pod Autoscaler is a built-in component that can handle this automatically. In Kubernetes, this is equivalent to scaling a deployment to add more pods. To deal with increasing requirements, such as high traffic, you can scale out your application by running multiple instances. This typically falls under the category of “scaling” and can be broadly divided into cluster and application scaling. A Kubernetes cluster requires compute resources to run applications and these resources may need to increase or decrease depending on the application requirements.

Masstransit vs dapr