There is a lot of change in the Sitecore ecosystem right now. There are also many opportunities for customers to consolidate multiple platforms under one roof.
- Do you go fully SaaS with SitecoreAI?
- Is your business ready for a composable architecture?
- AI-driven content operations are a brand new opportunity, could you use this?
- Will SaaS platforms give me the savings and predictability I’m expecting?
All important questions. All real problems. All part of the future.
But that’s not where a lot of organisations are today.
Many are still running Sitecore XP at a global scale. Not as a legacy platform falling apart, but as the backbone of how content is delivered globally right now.
Multiple markets. Multiple integrations. Real traffic. Real uptime expectations.
For those teams, the conversation isn’t about “what comes next.”
It’s about “how do we operate what we have better.”
Disclaimer
Timing is key. Sometimes a customer might need to improve what they currently have in the short term. This happens before the long term is ready.
This series is about how to improve what you have before that jump.
Sitecore XP for many is still doing the heavy lifting
Across industries, XP continues to power:
- Global marketing estates
- Content-heavy experiences
- Multi-brand delivery
- Commerce integrations
- Regulated and compliance-driven platforms
These environments can’t simply jump to SaaS overnight. Not because teams don’t want to move ahead, but because reality gets in the way.
Complex integrations – Changing a central platform could require entire rebuilds to how they communicate
Legacy dependencies – A change for one platform may result in multiple other changes needed
Operational risk – Everything is working so why change it, this could be a fear
Budget – It can be expensive to move to a new or upgraded technology stack, can you even start this year
Organisational readiness – Is the business ready for this at the moment. The current platform took 5 years to build do they have appetite to do it again
Job Security – You have a large team for the legacy technology, what do we do now
Sitecore XP remains the operational platform. And it has to behave like a global one.
The real problem isn’t XP – it’s how you operate it
Sitecore XP is a solid and known platform that offers a comprehensive suite of tools. It’s scalability and flexibility make it an ideal choice for companies of all sizes. Generally Sitecore XP issues occur with the implementation not the actual platform itself.
However most XP implementations start in a single region. That’s sensible early on. It keeps infrastructure simpler and costs predictable.
Over time, though, expectations change. As your business grows you start getting customers from global locations. Even the smallest deployment or change could have a big impact on your business.
And slowly, the delivery layer becomes the pressure point.
Not because XP can’t scale.
Because a single-region delivery model doesn’t.
Operating at scale is an operational challenge, not just an architectural one
When teams talk about “resilience,” they often jump straight to infrastructure. Regions. Load balancing. Failover.
But resilience in XP is just as much about the observability and control.
If you can’t see what the platform is doing, you can’t operate it confidently.
That’s why throughout this series, I’ll focus as much on monitoring and operational signals as I do on architecture:
- Using Application Insights to understand delivery behavior
- Defining rule sets that protect origins and enforce routing discipline
- Observing regional traffic patterns and failover in real time
- Validating deployments through telemetry, not assumption
This isn’t just about making the platform more available. It’s about making it understandable.
The delivery layer is where users feel everything
This is about strengthening the part of the platform users interact with every second.
I’m not talking about rebuilding or migrating XP in this series. Also this isn’t about migrating to SaaS.
This is purely about content delivery.
Because that’s where:
- Downtime is visible
- Performance is felt by customers and they react
- Deployments can be a pain for developers to manage and fix
If delivery becomes predictable, the entire platform feels more stable. Even if the underlying architecture hasn’t dramatically changed.
There’s a difference between having a Sitecore platform and operating it at scale.
That’s the maturity shift this series is really about.
What this series will explore
I’m going to focus on the practical steps that make XP behave like a global delivery platform.
Not theoretically. Operationally.
This is about making XP calmer under pressure.
This isn’t anti-SaaS – it’s pro-reality
Many teams will move toward SitecoreAI, composable architectures, and AI-driven content operations.
But those transitions take time.
In the meantime, XP continues to deliver real experiences to real users.
The question isn’t
what replaces it?
The question is
how do we make it stronger while it’s still carrying the load?
That’s what operating XP at scale means.
What’s next
We start by stabilising delivery.
Then we build operational confidence.
Then we prove resilience.
And we do it using the platform you already run.
Tim's Blog 
Leave a Reply