Architect for Scale: How Serverless Inference Changes AI Deployment | Jon Alexander, Akamai
Watch on YouTubeVideo summary
Organizations often face significant challenges when attempting to untangle their existing infrastructure and transition toward a distributed model, a hurdle that Akamai aims to simplify so enterprises can focus on business outcomes rather than complex plumbing. A key decision in this cloud journey involves early architectural choices; if applications are tied too closely to a single availability zone, region, or database location from the start, organizations will encounter substantial difficulties later on. This principle applies equally to artificial intelligence, where failing to plan for distribution can lead to rigid systems that are hard to scale or adapt as needs evolve.
Akamai has heavily invested in serverless technology as a fundamental approach to compute and infrastructure, believing it is crucial for widespread AI adoption. The company is currently developing a serverless inference platform designed to be consumed as a service, allowing customers to deploy models without worrying about specific locations, the number of regions involved, or placement details. By abstracting these underlying complexities, Akamai enables businesses to run AI workloads across many different locations seamlessly, ensuring that the infrastructure supports growth without requiring constant re-engineering of the core system.
The most effective strategy is to architect with future scalability in mind, even if the initial deployment occurs in just one region on day one. While it is not necessary to build out all potential infrastructure immediately, having a clear pathway and plan for expansion to two, five, or even hundreds of locations provides essential optionality for later growth. This forward-thinking approach prevents organizations from being locked into suboptimal configurations and allows them to scale their AI deployments efficiently as demand increases across the globe. Ultimately, planning ahead ensures that early decisions do not become bottlenecks, enabling a smooth transition to a robust, distributed AI environment.
Read the full video transcript
How hard is it for organizations to
untangle their current setup and move
towards a distributed model and how can
Akamai
make that easier so enterprises can
focus on business outcome and not all
the plumbing involved?
>> Again, I think I think this is one one
of the
kind of key decisions that everyone has
part of that that cloud journey as well.
So, I'm not sure this is different than
people have seen before.
If you make the right architectural
decisions up front, if you think about
where you want to end up, you can
architect
in the cloud to be able to deploy and
run in in many locations. Um
but if you make certain set of decisions
early on, if you tie your application to
a single availability zone or a single
region or a single database location,
then you you really end up with
challenges. And I think that the same is
true for AI. Um we've
we've heavily invested in serverless as
one of the kind of fundamental
presentations of of compute and
infrastructure that we think is going to
be incredibly important for for AI
adoption. And we're we're working a lot
right now in our road map on on building
a serverless inference platform
that customers can just consume as a
service and they don't need to think
about where something's running, how
many locations, they don't need to think
about that placement. Um so, I think
that's the type of advice I would give
is if you
architect
and tie to just one location, yeah, you
you you you're going to have problems.
You're going to have to uh unwind a lot
of those decisions you made early on.
If you're making decisions where even if
you are deploying into one region on day
one, but if you've got a plan of how you
could scale this out
to two locations, five locations, 10
locations, 20
100 locations,
um
you'll be fine. So, again, it's planning
planning ahead. You don't need to build
all of that uh infrastructure on day
one,
but at least having a a pathway is going
to give you the optionality later on.