← All posts

Learning the rest of the Adobe stack as a commerce architect

What I’m learning about AEM, AEP and Journey Optimizer, where commerce fits in the bigger picture, and the advice I’d give another commerce architect starting out.

On this page · 4 sections
  1. What I’m learning
  2. What surprised me
  3. Where commerce fits
  4. Advice for another commerce architect

Commerce is one part of the customer experience. For most of my career I’ve designed that part, and designed it well. Lately I’ve been learning the rest of the Adobe stack, so I can design the whole picture instead of one box in it. This blog has been part of that: the App Builder series is me doing the learning in public.

What I’m learning

  • AEM (Adobe Experience Manager): content and experience management, and Edge Delivery Services for fast storefronts.
  • AEP (Adobe Experience Platform) and Real-Time CDP: unified customer profiles built from every touchpoint, and audiences built from those profiles.
  • Adobe Journey Optimizer: orchestrating messages and experiences across channels from those profiles.

What surprised me

Commerce architects already think in data flows, events and integration contracts. That carries over well. What’s new is the scale of the customer data, and how much of the work is governance: consent, identity, data usage labels and who may use which data for what.

The hardest part of enterprise architecture isn’t the systems. It’s agreeing what the data is allowed to do.

Where commerce fits

Commerce produces some of the most valuable signals a business has: what people browse, buy, abandon and return. In an enterprise design, it becomes a source of truth for transactions and a rich stream of events for everything else. Designing those events well is a commerce architect’s best contribution to the bigger picture.

Advice for another commerce architect

  1. Learn the vocabulary of each product before the features. Profiles, schemas, datasets, journeys.
  2. Map one real customer journey end to end, across every system, and see which parts you don’t understand.
  3. Build something small in each product. Reading only gets you halfway.
  4. Write it down. Teaching is the fastest way to find the gaps in what you know.

That last point is why this blog exists (how it got built is its own post). Thanks for reading along.

Written by Vishwas Bhatnagar

Technical Architect. Adobe Commerce, marketplaces and AI-assisted engineering.

More about me →

More