Customers
Resources
analyst-report.svg

Analyst Reports

Navigating Key Metrics for Growth and Success

blog.svg

Blog

Source for Trends, Tips, and Timely Topics

docs.svg

Documentation

The Blueprint for Mastering Tools and Processes

sandbox.svg

Sandboxes

Explore interactive sandboxes for Avesha products

line
news.svg

News/Pubs

Bringing You the Top Stories as They Happen

videos.svg

Videos

Explore Our Library of Informative and Entertaining Clips

whitepapers.svg

Whitepapers

Exploring Critical Topics with Authoritative Research

roi.svg

ROI Calculator

Easily Track and Maximize Your Investment Returns

line
egs-marketing

Optimize Your AI with Elastic GPU Service (EGS)

Company
about-us.svg

About Us

Discover Our Mission and Core Values

careers.svg

Careers

Join Our Team and Shape the Future Together

events.svg

Events and Webinars

Connecting You to Trends, Tools, and Thought Leaders

support.svg

Support

Helping You Navigate Challenges with Ease

FAQ
myth_or_mantra.jpg
Raj Nair

Raj Nair

Founder & CEO

15 July, 2024,

1 min read

Copied

link

#1 Myth or Mantra of spike scaling – “throw more resources at it.” Is there a better way? Imagine scaling up a microservice that’s upstream of a chokepoint without first investigating the bottlenecks. Picture simulating various traffic conditions to figure it out, all while struggling to maintain a fast product delivery schedule within budget constraints. How many of you grapple with these challenges every day?

During a recent webinar, the conversation turned to the often-ignored difficulties of delivering SLOs and SLAs in cloud environments. One guest, a CTO managing weekly events, vividly described the human cost of stress on engineers handling unpredictable traffic spikes. His team spends 40 man-hours preparing a single application for an event, only to have SREs monitor scaling through the night. The frustration in his voice was palpable as he spoke of SRE burnout. “Humans aren’t particularly good at knowing what to scale in an application with hundreds of microservices. They can’t keep all the dependencies in their heads.”

Could RLHF (Reinforcement Learning with Human Feedback) be the answer? Picture an event co-pilot, an AI that not only calculates the precise scaling needed for each microservice but also dynamically adjusts in real-time to traffic conditions. This AI, envisioned by the CTO, would alleviate the stress on SREs through disciplined, dependency-aware scaling, balancing the workload and promoting sustainability. The alternative—scaling everything uniformly—could inadvertently create new bottlenecks and prevent getting the SLA/SLOs.

What are your thoughts on reducing SRE stress from managing infrastructure for events?

Related Articles

card image

Scaling RAG in Production with Elastic GPU Service (EGS)

card image

Optimizing GPU Allocation for Real-Time Inference with Avesha EGS

card image

#1 Myth or Mantra of spike scaling – "throw more resources at it."

card image

Do You Love Your Cloud Credits? Here's How You Can Get More…

card image

The APM Paradox: When Solution Becomes the Problem

card image

Migration should be 'gradual' and 'continuous'

card image

Hack your scaling and pay for a European Escape?

card image

Here Are 3 Ways You Can Slash Your Kubernetes Costs by 50%

card image

A completely new way for K8s Autoscaling: Why Predictive Pod Scaling with Smart Scaler and Karpenter is needed before plain VPA

Copyright © Avesha 2024. All rights reserved.

Terms and Conditions

Privacy Policy

twitter logo
linkedin logo
slack logo
youtube logo