The underlying architecture of a Composable DXP is known as MACH—a set of technology principles that stands for
M = Microservices-based,
A = API-first,
C = Cloud-native,
H = Headless.
MicroservicesEach piece of a Composable DXP is a microservice, independently developed, deployed, and managed. For example, email marketing is a microservice, CDP is a microservice, and so on.
APIA Composable DXP uses APIs to communicate between components. Most often, a RESTful API will be used to communicate and integrate microservices. REST defines a set of constraints for the architectural behaviour of an internet-scale distributed hypermedia system, such as the web.
CloudA Composable DXP leverages the full capability of the cloud. Beyond storage and hosting, this provides elastic scaling and high availability of Sitecore services. Functionality is updated manually by the service owner, to eliminate your need to upgrade. So cool or?
HeadlessIn a Composable DXP, front-end UX is completely decoupled from back-end logic, allowing for complete design freedom in creating your front-end user interface. In addition, headless also provides the capability for omnichannel publishing to existing applications like IoT, artificial reality, vending machines, sensors, billboards—really any place you want to display frontend.
Post a Comment
a new comment