Scaling I/O Bound Microservices

Scaling I/O Bound Microservices

Table of Contents

In this meetup, we will continue our #2ndhalf journey to the next^2. You can see the talks from the 1st meetup of this series here - http://bit.ly/second-half-p1 Nowadays, scaling and auto-scaling have become relatively easy tasks. Everyone knows how to set up auto-scaling environments - Auto-Scaling groups, Swarm, Kubernetes, etc.

But when we try to scale I/O Bound workloads: Message queues (Kafka, Rabbit, NATS) Distributed databases (Hadoop, Cassandra) Storage subsystems (CEPH, GlusterFS, HDFS), the traditional auto-scaling mechanisms are just not enough.

Heavy calculations must be performed to determine the I/O bottlenecks. Rebalancing the data after a scaling event can take up to hours depending on your data & could, resulting in data loss if not properly designed.

We will deep dive into this type of workload and walk you through code samples you can apply in your own environment.

Video


Presntation slides

comments powered by Disqus

Related Posts

Planning a production ready kubernetes with fundamental Controllers & Operators — Part 4

Planning a production ready kubernetes with fundamental Controllers & Operators — Part 4

Originally posted on the Israeli Tech Radar on medium.

Welcome back to part four of our series on building a production-ready Kubernetes cluster with fundamental controllers and operators! In the previous parts, we explored essential components like Secrets and DNS management. Today, we’ll delve into the world of Ingress, a critical concept for routing external traffic to your applications within the cluster. To explain Ingress, I’ll be taking the Analogy approach, I’ll use the analogy of a city compared to a modern distributed computer:

Read More
From Prompts to Agents — a DevOps Engineer navigating the AI Landscape

From Prompts to Agents — a DevOps Engineer navigating the AI Landscape

TLDR; A.I is no longer a futuristic concept; it’s fundamentally changing how we work today. For those of us specializing in DevOps, SRE, and platform engineering, this shift presents both incredible opportunities and new challenges. We’ve moved quickly from debating if AI will impact our work to figuring out how to effectively integrate it and adapt our skillsets to stay relevant and valuable.

Read More