Event-Driven Commerce Has Sharp Edges
EventBridge schedules, SQS workers, and domain Lambdas scale side effects, while teaching hard lessons about ordering, backpressure, and figuring out what already happened.
Leadership, mentoring, and deep notes on the commerce platforms, specialty ops systems, AWS, and delivery habits behind calm teams.
EventBridge schedules, SQS workers, and domain Lambdas scale side effects, while teaching hard lessons about ordering, backpressure, and figuring out what already happened.
Large catalog moves look like ETL. The hard parts are identity mapping, partial cutovers, image/media reality, and keeping orders flowing while the universe relocates.
Auth, gateway, orders, locations, users, and POS apps can be separate deployables, but only if the boundaries match real change rates and failure domains.
Turning external B2B payloads into Shopify orders looks like “call the API.” The real work is validation, enrichment, idempotency, partial failure, and telling someone what happened.
Lambdas and Remix loaders tempt you to write scripts. Complexity shows up when validation, I/O, and domain rules share one file, and nobody can test the part that matters.
Shared modules are not a style preference. They are how teams keep AWS platforms reviewable after the third service and the second environment.
Behind specialty POS sits an operating system: Next.js associate portals, an Express webhook platform, and cron jobs for exports, pending cleanup, FTP, and sync. Here is what that system actually contained.