The recordings of the SUGCON event are now available including the keynote that Jason and I delivered on Friday morning.
Composable DXP is all the rage, but what if you already have a platform installation with years of investment into getting it just how you like? How do you gradually move your architecture over to something that is MACH and headless? Do you need a full rebuild? Do you need Next.js or not? Where does content go now? What are the benefits and downsides?
Pieter Brinkman (@pieterbrink123) and Jason St-Cyr (@StCyrThoughts) take an overview of a few XM and XP scenarios and how you can gradually migrate to a composable architecture, along with some of the advantages and disadvantages of different options.
Composable DXP is all the rage. Why is the industry moving towards SaaS and Composable architecture? What are the benefits of composable for customers? And is composable for everyone. These are all questions that are addressed in the Architecture guide to SaaS video.
Next to that we’re also addressing that the actual migration. What if you already have a platform installation with years of investment into getting it just how you like? How do you gradually move your architecture over to something that is MACH and headless? Do you need a full rebuild?
This week I had the pleasure to talk with Himadri from Nishtech about Sitecore’s SaaS journey and how we are moving to the Composable DXP.
Nish Tech digital bytes outline
When you think of a traditional digital experience platform, you probably think of a monolithic, tightly coupled full-stack suite from a single vendor that allows you to manage the entire digital experience, from content management to digital marketing and analytics. But maybe you don’t need all that. The concept of a composable DXP allows you to create a custom solution using technology that fits your needs and works with your existing processes and infrastructure.
In this episode we’re excited to welcome Sitecore Senior Director of Technical Marketing Pieter Brinkman to discuss his thoughts on the composable DXP and how it fits into Sitecore’s roadmap.
If you follow the Digital Experience Platform (DXP) and web industry you seen that the industry is slowly moving away from Platform DXP’s to something called a Composable DXP.
In this article I want to address a few questions that I get asked a lot, including:
What is a Composable DXP?
What is the difference between a Composable DXP and a platform DXP?
What are the key benefits of a Composable DXP.
Here we go!
What is Digital Experience Platform (DXP)?
Industry research and advisory firm Gartner defines DXP as:
“A digital experience platform (DXP) is an integrated set of core technologies that support the composition, management, delivery and optimization of contextualized digital experiences.”
A DXP consist out of three main pillars:
Content is the main foundation of DXP. It’s the starting point and the fuel of everything. You need content to drive Digital Experiences. The content pillar is all about content strategy, creation, collaboration and making the content available for consumption.
The Experience pillar is where we build digital experiences. This includes tools for Analytics, Marketing Automation, Personalization and optimization. The content is powering the experiences.
The final pillar is Commerce. With the commerce pillar we add the possibility to add conversion to experiences.
A good DXP solution combines Content, Experience and Commerce to maximize impact.
That brings us to the next questions; What is a Composable DXP and what is a Platform DXP and what are the differences?