Technology
An editorial conversation with Bryan House, Chief Executive Officer at Elastic Path
Over the last year, a quiet question has surfaced in B2B commerce conversations. It doesn’t appear on conference stages or in trend reports. It appears in side conversations with digital leaders and architects who have experienced at least one platform cycle.
People are wondering if composable commerce is making a comeback.
Architecture isn’t failing, but it is changing shape. To explore why, I sat down with Bryan House, Chief Executive Officer at Elastic Path. Bryan has watched multiple architectural cycles, moving through tightly coupled platforms, the headless enthusiasm of the late 2010s, and the composable era teams are in today.
Our discussion focused on where reality is asserting itself over architectural theory.
“This doesn’t feel like a reversal”
One of the first things Bryan noted was that the market isn’t abandoning composable principles.
“This feels like teams recalibrating based on what they’ve learned,” he said. “It doesn’t feel like a swing back to monoliths.”
Composable architecture delivered flexibility and modularity. For organisations with high engineering maturity, the ability to evolve without rebuilding everything from scratch remains a significant advantage. The tension appears in the day-to-day operations.
“As stacks grew, so did the coordination required to keep them moving,” Bryan explained. “Each service made sense on its own, but the system as a whole became harder to operate.”
When flexibility meets fatigue
Our conversation kept returning to a familiar operational pattern. Fully composable stacks offer freedom but introduce a steady accumulation of decisions: vendor selection, integration ownership, release coordination, and support paths. These aren’t insurmountable, but they create drag.
I’ve compared shopping for technology to a weekly grocery run before. Composable commerce can feel like visiting ten speciality shops to make a single meal. The quality is high, but the logistics eventually wear you down.
Bryan agreed. “We hear that from teams a lot. They weren’t chasing complexity; they were trying to avoid rigidity. But at some point, the overhead becomes the constraint.”
Why bundling is re-entering the conversation
Teams aren’t questioning composable principles; they are changing how they respond to them. Many are looking for ways to reduce architectural load early while preserving optionality for the future. This is why bundled composable approaches are appearing more frequently.
“Teams want to get moving without closing doors,” Bryan said. “Bundling core capabilities simplifies the starting line. The escape hatch is still there if and when it’s needed.”
This matches architecture to organisational capacity. For manufacturers and distributors with finite engineering resources, starting with a pre-integrated core prevents the team from becoming the “glue” that holds ten different vendors together.
The real issue isn’t architectural
At one point, the conversation shifted away from platforms entirely.
“The biggest challenges we see aren’t architectural,” Bryan said. “They’re organisational. Ownership, accountability, and adoption.”
I’ve seen B2B teams struggle not because they chose the wrong technology model, but because no one owns the end-to-end experience once it’s live. Composable systems amplify this reality. When teams are aligned, they move quickly. Without that alignment, flexibility turns into friction.
So… is composable commerce swinging back?
The market is learning to apply composable commerce with more restraint.
Teams are bundling where speed and simplicity matter. They are decoupling only where differentiation pays off. They are making fewer decisions for architectural purity and more for long-term sustainability.
As Bryan put it, “The goal was never to build the most elegant system on paper. It was to build something teams can run, improve, and customers actually want to use.”
This is a settling point shaped by experience, rather than a swing backwards.