PlatformIntegrationsResourcesDocsPricing
ContactLog inSign up
Intro to Composable Architecture
The Modern Enterprise Stack
The Rise of Composable Architecture
Key Parts of a Composable System
Microservices & Serverless Functions
How Microservices Work
Benefits of Microservices
Challenges of Microservices
Serverless Function Providers
The Backend: Databases & Headless CMS
Working with Composable Content
Types of Backend Services
Benefits of Decoupled Content
Common Challenges with Decoupled Content
Choosing the Right Backend Service
The Frontend: Web Frameworks
The New "Frontend"
Site Framework Considerations
Modern Frameworks for Enterprises
Content Editing in Composable Systems
Editing Experience in Monolithic Systems
Headless Editing Experiences
Visual Editing Services
Composable Content
Multi-channel Developer Challenges
Homegrown Content Meshing Solutions
Vendor-based Composable Systems
CI/CD: Building, Deploying, & Hosting
CI/CD for Monolithic Applications
The Build Pipeline
Build & Deployment Services
Common Website Features & Tooling
Authentication
Analytics
Personalization & A/B Testing
Form Submissions
Search
Common Enterprise Challenges
Technology Cost
Security
Traffic & Scalability
Page Speed Performance
Code Complexity
Continuous Integration & Delivery
Getting Started: Migration Strategies
Gradual Migration
Evaluating Tools & Services
Wrapping Up: Is Composable Worth It?

Vendor-based Composable Systems

Homegrown Content Meshing SolutionsCI/CD: Building, Deploying, & Hosting
Trust CenterPrivacySecurityGDPR/CCPAAbuse
©2023 Netlify
On This Page
One-way content mechanism
Leveraging the platform

As a result of the challenges with building internal content middleware systems, we’ve seen a new category of service emerge in the last few years. The terms in this space are widespread and changing, but are most commonly referred to as digital experience platforms (DXP) or compositions (DXC).

One-way content mechanism

While we're still in the early days for many of these tools, there's one thing that has become clear — reading content stitched together through an API is not enough. A composable system isn't just about developer conveniences, but about finding efficiencies so that your website can achieve its goals on every level.

Content middleware must be able to both read and write from the content source. And it should be easily wired up to a visual editing experience so that content editors only need to use a single application to edit content.

Most DXC and DXP providers do not offer this ability without getting locked into using other tools and services.

Leveraging the platform

In a monolithic system, the strength of every component in the system is subject to what the service provider could deliver and support.

In a composable system, the strength of every component feels limitless, but comes at the expense of managing each tool or service individually, which can often include building and maintaining underlying infrastructure.

Composable platforms like Netlify are designed to help you continue to work with the tools and services your organization prefers, while lessening the low-level burdens of stitching all these services together.