Discuss a project

DL-043 · Case study

Amazon and Walmart API architecture review for an eCommerce SaaS

A software platform serving marketplace sellers needed to resolve integration instability before onboarding more customers.

Client
Name withheld
Location
Singapore
Industry
B2B SaaS / Marketplace software
Capabilities
01Audit02Stabilize
01

Challenge

  • Growing account volume exposed API throttling, delayed jobs and inconsistent synchronization.
  • Shared processing queues allowed individual accounts to affect unrelated customers.
02

Environment

  • Amazon SP-API and Walmart Marketplace APIs.
  • Multi-tenant Node.js services, PostgreSQL, Redis and AWS.
03

Intervention

  • Audited authorization, rate-limit handling, job scheduling and retry behavior.
  • Designed per-tenant workload isolation, idempotent processing and adaptive backoff.
  • Introduced an observability specification covering backlog age, API errors and synchronization freshness.
04

Outcome

  • A stabilization roadmap prioritizing data correctness and tenant isolation.
  • A scalable foundation for subsequent marketplace integrations.
Independent tenant queues, marketplace adapters and centralized monitoring.TENANTSSeller accountsTENANT QUEUESIsolatedAPI WORKERSBackoff / retryMARKETPLACE APISAmazon / WalmartMONITORINGBacklog / errors
  1. 01TENANTSSeller accountsTENANT QUEUESIsolated
  2. 02TENANT QUEUESIsolatedAPI WORKERSBackoff / retry
  3. 03API WORKERSBackoff / retryMARKETPLACE APISAmazon / Walmart
  4. 04MARKETPLACE APISAmazon / WalmartMONITORINGBacklog / errors
Fig. 01Multi-tenant API processingIndependent tenant queues, marketplace adapters and centralized monitoring.Scale NTS

Stack and services.

Stack07

  • Amazon SP-API
  • Walmart Marketplace API
  • PostgreSQL
  • Redis
  • AWS
  • Node.js
  • EDI

Services used03

Tell us what has to work.

A senior engineer reads every brief. Describe the system, what it runs on today and what happens when it fails.

Discuss a project