Discover · slack.engineering

Slack AI: The Path to Multi-Cloud

Slack Engineering slack.engineering

This is what was read here when it was published. Shaurya Kethireddy no longer carries it in what it publishes now.

In early 2023, Slack faced a foundational challenge: serving Large Language Models (LLMs) at enterprise scale with the security, reliability, and performance our customers expect. Over three years, we evolved from basic infrastructure to orchestrating a sophisticated multi-cloud architecture. We didn’t just want shiny new models; we needed a system resilient to regional outages and GPU scarcity. Our journey moved through four distinct phases, shifting from reactive infrastructure management to proactive, multi-vendor orchestration.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Names and references

  1. Cloud — person
  2. Path — person

In the piece

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

More like this

Also from Slack Engineering

  1. Shipyard: How We Built Slack’s Next-Generation EC2 PlatformArchie Gunasekara slack.engineering
  2. Agentic Testing: Where Agents Fit in the E2E Testing StackSergii Gorbachov slack.engineering
  3. From SSH to REST: A Security-Driven Modernization of Slack’s EMR Data PipelinesMahendran Vasagam slack.engineering
  4. Managing context in long-run agentic applicationsDominic Marks slack.engineering
  5. From Custom to Open: Scalable Network Probing and HTTP/3 Readiness with PrometheusCarlo Preciado slack.engineering
  6. How Slack Rebuilt Notifications 📣Frances Coronel slack.engineering