Did you miss it live? We've got your back! Click below to watch of the interview segment of this session on YouTube.
Watch Full Interview on YouTube
Introduction
At this session, we had the privilege of exploring the mind of John West — a software architect, former Sitecore CTO, and now a visionary behind Orchex. Our conversation stretched across John's personal journey, his philosophy on technology and community, and the pressing architectural challenges facing today's enterprise software landscape. This post recaps that wide-ranging discussion, sets the foundation for understanding Orchex's unique approach, and invites you to join a movement focused on creating orchestrated, composable enterprise solutions.
The Power of Perseverance: Why Good Deeds Lead to Lasting Success
Watch Full Interview on YouTube
1. Who is John West? A Journey Driven by Curiosity and Community
John’s story starts with a Commodore 64, a black-and-white TV, and a deep, early fascination with programming. Though he initially pursued psychology, John's passion for computing never waned. His first big break came working in Electronic Data Interchange (EDI) at Xilinx, where he interfaced with every part of the business — from inventory to finance. This experience shaped his understanding of robust, fail-safe systems where reliability wasn't optional.
Later, John moved into consulting, cutting his teeth with Interwoven in the early days of web content management systems (WCMS). His curiosity and drive for paradigm shifts led him to Sitecore, where he found a new architectural model — moving from files to object trees — that drastically increased productivity. His approach was always community-first: sharing knowledge freely, blogging solutions, and helping developers succeed.
But as Sitecore grew and commercial pressures increased, John felt the culture drift away from its original customer-centered ethos. This internal tension — between integrity and market forces — eventually led him to step away, setting the stage for Orchex.
2. Architectural Shifts: From Monoliths to Composable... and Beyond
From Monoliths to Composable Chaos: Why Orchestration is the Missing Link
Watch Full Interview on YouTube
In enterprise software, architectural paradigms matter. John’s journey mirrors the evolution of these paradigms:
-
Monolithic Applications (e.g., Sitecore):
Early on, platforms like Sitecore bundled all capabilities (content, analytics, commerce) into one big system. This promised convenience but often resulted in brittle, bloated solutions that locked customers in and burdened developers with rigid architectures. -
Composable Architectures (Headless, Jamstack, etc.):
Composable promised a better way: select best-in-breed solutions and stitch them together. However, John points out that while composable offers flexibility, it also brings a serious risk of spaghetti integration — complex, fragile, point-to-point connections without a unifying system to manage them. -
Orchestration: The Missing Layer
True enterprise-grade solutions need more than just APIs talking to each other. They need a brain — an orchestration engine — that:- Decouples systems intelligently
- Manages data flows
- Provides resilience and adaptability
- Allows you to pivot vendors or platforms without tearing everything apart
- Offers an “operating system for composable enterprises”
Without orchestration, John warns, composable solutions will crumble under their own complexity.
3. Orchex: A New Approach for the Composable Enterprise
This realization gave birth to Orchex. Here's how Orchex redefines the game:
-
Open Source Core:
Orchex is open because control matters. Enterprises need to own their orchestration layer — not be beholden to a SaaS vendor’s fate or price hikes.
Why Open Source Matters: Reducing Enterprise Risk the Right Way
Watch Full Interview on YouTube
-
Domain-Driven, Vendor-Neutral:
Instead of coupling directly to specific vendor APIs, Orchex uses adapters. You model your business needs (e.g., a commerce flow) and then plug vendors into those slots — reducing lock-in and future-proofing your architecture. -
Built for Community:
Much like the early Sitecore days, Orchex aims to be shaped by practitioners. It's not just about building software; it's about building a movement where professionals contribute, adapt, and improve the platform together.
4. Join the Orchex Movement: Build the Future Together
Beyond Success: John West’s Mission to Empower a More Inclusive Tech Industry
Watch Full Interview on YouTube
The future of enterprise software can’t be left to siloed companies or ivory-tower architects. It needs a community — us — to shape it.
We invite architects, developers, vendors, and visionaries to be part of the Orchex movement. Whether you're solving integration nightmares today or planning tomorrow’s composable enterprise, your ideas, challenges, and contributions matter.
👉 Ready to join the movement?
Reach out to the Orchex team at https://www.orchex.org/
Let's build better enterprise solutions — together!