[nicholasjarnold]

When you say "SF is pushing a microservices architecture for e-commerce hard", I wonder if you mean they attempt to rope customers into buying into the Mulesoft ecosystem (most of which, btw, is old versions of Spring on old JVM under the hood). They now own Mulesoft, and there is an army of sales people whom are presumably really good at getting the execs excited for groundbreaking features like "API Governance", "API Gateway", "low-code" and my favorite "security".

A company I worked with suffered some serious setbacks after a lot of promises, many months and many many millions burned on this stuff. I'll be a happy man if I never have to hear about SAPI/BAPI/CRAPPI from ProServices people that don't even understand their own products let alone sound engineering principles again. I must admit that I wasn't directly involved with SF/Mulesoft impls, but I did suffer through many regrettable touch points with it.

[theandrewbailey]

> When you say "SF is pushing a microservices architecture for e-commerce hard", I wonder if you mean they attempt to rope customers into buying into the Mulesoft ecosystem

Yup, bingo!

Before I got laid off, I was working on... monolithic (for the lack of a better term) SFCC systems, never headless. The vast majority of the few SFCC job postings I've come across have been asking for Mulesoft experience, and that summer job also featured it, though I never worked directly on it, only the SFCC instances that sat behind it.

I've never worked with any Salesforce sales team prior to actually getting to work, and in fact, all of my work in the past 7-ish years (and most of it before) has been post-launch development and support.

EDIT: And when I started looking at what Mulesoft was, why, and how to use it, all I found was hype about APIs; nothing about why you would point web browsers at it for HTML. The documentation might as well have said it was a genie that made all your wishes come true.