Architecture

Internal traffic should travel an independent path at every layer – gateway, pods, database – not just live behind a different URL prefix.

Business Critical’s complimentary reader is great until you have more than one read workload. Hyperscale named replicas give each workload its own endpoint.

Event-driven sync drifts. Pair it with a cheap periodic dump-and-diff and you get reconciliation almost for free.

Go is a fine language for infrastructure tooling. But for the 90% of software that is business applications, Spring Boot’s developer experience is dramatically superior – and AI-assisted development has eliminated the last argument against Java’s annotation-driven model.

Oracle ATG Commerce is legacy now, but its Nucleus component model, immutable repository items, and config layering were ahead of their time. Its distributed locking, custom messaging, and datasource switching were not. A reflection on what held up and what didn’t.

The identity industry is stuck between SaaS IDPs that aren’t flexible enough and custom solutions that aren’t secure enough. And for a surprising number of applications, the entire OAuth2 token ceremony is overkill – a session cookie would do.

HAProxy sidecars for mTLS. Hystrix for circuit breaking. Apache Camel between layers within the same service. Six API versions. A mandated common framework. A squash merge ban. Each decision was defensible. Combined, they created a system that took three months to onboard into.

HTTP status codes are a contract consumed by clients, load balancers, monitoring, and caches. When you return 200 OK for partial failures, every one of these systems is blind.

SAP Commerce OCC promises a stateless REST API for headless commerce. Underneath, every request hydrates an HTTP session and routes through the same stateful facades built for the JSP storefront. The API is stateless in contract but stateful in implementation.

The SAP Commerce Converter/Populator pattern optimized for extensibility at the cost of predictability. Deep chaining, invisible runtime graphs, and JVM heap exhaustion are the consequences.