Feb 10
Loading video player...
In this lecture, we dive into the low level design of microservices, focusing on their internal structure and responsibilities. We explore essential system design aspects, including the User Service for managing profiles and authentication, and the Product Service for handling catalogs and stock. This session is crucial for understanding robust backend development and applying sound software architecture design principles. we move from High-Level Design (HLD) to Low-Level Design (LLD)—the part where your microservices become real. LLD is all about defining the internal structure, boundaries (bounded context), responsibilities, data flow, and API contracts for each microservice so services don’t overlap or “leak” responsibilities. We’ll break down what each service owns in our e-commerce architecture: User Service (onboarding, auth, profiles, role-based authorization), Product Service (catalog, categories, inventory/stock), Order Service (cart + order lifecycle, orchestration with payment events), Payment Service (payment gateway integration, refund/chargeback flows, status notifications), and Notification Service (consume events and send email/SMS asynchronously). You’ll also see the core technology choices for implementation: Go + Fiber for backend APIs, React for frontend, PostgreSQL for structured data, S3 for file storage, gRPC for synchronous communication, Kafka for async events, and Elasticsearch for fast product search. Finally, we’ll sketch the database schema and relationships (users, addresses, carts, orders, products, payments) so you understand how data connects—then we’ll split it properly per microservice during implementation. 📚 CHAPTERS 00:00 What Low-Level Design (LLD) focuses on 02:10 Bounded context and microservice responsibilities 05:10 LLD checklist: data flow, contracts, endpoints, schemas 07:20 User Service responsibilities (auth, profile, roles) 11:40 User Service endpoints (register, login, profile) 15:20 Product Service responsibilities (catalog, inventory) 18:10 Order Service responsibilities (cart + order lifecycle) 21:30 Payment Service responsibilities (gateway + refunds) 24:10 Notification Service responsibilities (events + email/SMS) 26:10 Tech choices (Go, Fiber, gRPC, Kafka, Postgres, S3, Elasticsearch) 27:40 Database schema overview + entity relationships 29:20 What’s next: start building microservices from this design #systemdesign #lld #microservices #backendengineering #softwarearchitecture #distributedSystems #grpc #kafka #golang #databaseDesign #ecommerce #cleanarchitecture