E-commerce platform. Core build principles, problems and guidelines.
summary
Argues an e‑commerce platform should use domain-driven design with microservices and database‑per‑service, handle distributed transactions with the saga pattern or alternatives like CQRS and event sourcing, and apply retries, circuit breakers and monitoring via Datadog/Grafana/Kibana. Describes a real migration: payments redirected to an external system using feature flags with a single central control flag, staged downstream-to-upstream rollout, prod data checks and rollback capability, which succeeds when logs, alerts and flag cleanup are enforced. Recommends decouple, refactor early, follow ISO 25010 reliability/performance/security.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:42BUILDING NORTH STAR METRIC
- 3:57DOMAIN DRIVEN DESIGN OF COMPONENTS
- 5:39CHALLENGE. DISTRIBUTED TRANSACTIONS
- 8:21PATTERNS. SAGA
- 10:08ALTERNATIVE PATTERNS
- 11:36STRATEGIES COMPAISON
- 12:52RELIABILITY PATTERNS
- 14:55RESPONSIBILITIES, BOUNDARIES AND SCOPES
- 17:30LEGACY FLOWS
- 19:57LEGACY CODE
- 23:16INTEGRATIONS
- 26:33PREREQUISITES
- 29:02PITFALLS
- 32:22RESOLUTION
- 36:47FLOW REPRESENTATION
- 42:17WHAT ECOMMERCE CAN GIVE YOU?
related talks
50mMicroservice specifics illustrated by an e‑commerce platform
56mArchitecting Cloud Native Microservices
46mMicroservices from the Trenches
43mCustomer-Focused Replatforming of an Existing Shop Monolith
43mThe hitchhiker's guide to software architecture and design
58mModernizing an existing system to take a more domain-driven approach
51mPatterns & Practices of Implementing Event-driven MicroSvc...
24mPatterns of Evolution from Monolith to Microservices