Feb 2024: Composability and Vertical Focus

A composable mindset with a focus on high-value verticals and outcomes.

4 min
Feb 2024: Composability and Vertical Focus

February 2024 reaffirmed Adobe's direction: composability with a pragmatic focus on outcomes. We saw investment in Adobe App Builder, API Mesh and Commerce Services that make it easier to extend core commerce with event-driven microservices, without collapsing back into a monolith. At the same time, Adobe highlighted vertical solutions - repeatable patterns for sectors where time-to-value matters as much as flexibility.

On the technical side, GraphQL coverage continued to expand, enabling cleaner headless front ends and B2B workflows (quotes, approvals, purchase orders) without brittle workarounds. App Builder brought predictable integration points for payment, tax, search and fulfilment, while API Mesh simplified stitching third-party APIs behind a unified schema. Together, these tools help teams create clearer system boundaries and reduce accidental complexity.

For merchants, the message was simple: adopt a composable mindset, but measure success by customer and operational outcomes. Faster product discovery, improved conversion, reduced returns and lower cost-to-serve are the metrics that justify the architecture. Composability is not a goal; it is a means to ship faster, scale better and adapt without replatforming every two years.

Where we see value land quickly is in integration clarity. Define contracts, SLAs and error budgets between services. Instrument everything and establish performance baselines for search, PDP, cart and checkout so you know when a change degrades experience. For B2B, map approval chains and permissions into tests so PO and quote flows remain reliable as you iterate.

Practical guidance:

  • Start with one or two high-impact services (e.g., search, recommendations) integrated via API Mesh; prove the value before decomposing further.
  • Use App Builder for event-driven extensions (order placed, shipment created) to avoid custom cron jobs and long-running app servers.
  • Create runbooks for failure modes and rollback paths; rehearse them on staging with production-like data.
  • Add synthetic and RUM monitoring to headless front ends; track p95 metrics for key journeys.
  • Treat data privacy and access control as first-class concerns across services from day one.

Done well, composability reduces change friction and shortens the path from idea to impact. February's updates make that path more accessible - provided teams keep the focus on measurable results.

Want to read more insights?

View All Articles
Feb 2024: Composability and Vertical Focus | Tom&Co