System Design and Architecture
4.0
(0)
10 learners
What you'll learn
This course includes
- 10.5 hours of video
- Certificate of completion
- Access on mobile and TV
Course content
1 modules • 53 lessons • 10.5 hours of video
System Design and Architecture
53 lessons
• 10.3 hours
System Design and Architecture
53 lessons
• 10.3 hours
- Microservices with Databases can be challenging... 20:52
- Deep Dive into REST API Design and Implementation Best Practices 12:02
- Domain-Driven Design: The Last Explanation You'll Ever Need 21:05
- The Outbox Pattern is seriously underrated... 15:37
- How does Caching on the Backend work? (System Design Fundamentals) 22:45
- A Beginner's Guide to Event-Driven Architecture 37:28
- API Gateway vs Load Balancer vs Reverse Proxy: when to use what? 09:06
- Idempotency in APIs: you should be aware of this! 07:31
- How do large teams scale their Frontend applications? 07:47
- Think Multi-Tenancy Is Easy? Think Again... 14:59
- Common Application Architecture Types Explained #Shorts 00:59
- I explain "EventStorming" with real examples 13:23
- Here's when Event-Driven Systems should REALLY be used.. 08:02
- Do DTOs Even Make Sense Anymore? 14:45
- The Ultimate Guide to Load Balancers (System Design Fundamentals) 11:05
- How to use a Circuit Breaker to make your API more resilient? 11:34
- Here's why implementing a Payment System can be so hard 11:27
- How modern backends handle heavy payloads (Claim-Check Pattern) 08:32
- Is Service Mesh a MUST-HAVE for your Microservices? 09:14
- Caching challenges that scare even senior engineers 16:15
- "Backends for Frontends": what is it? 07:41
- A better alternative to plain Microservices (Self-Contained Systems) 15:22
- How do microservices find each other's IP addresses? 08:05
- Why do backends need Change Data Capture? 13:56
- The Hardest Problems in Event-Driven Architectures 16:37
- Should you choose a Hexagonal Architecture for your next project? 09:48
- How to become a Software Architect in the AI Era? 10:01
- Deep dive into Dead-Letter Queues 15:08
- How to make your application scalable? 12:16
- Can an "Anti-Corruption Layer" save your bad software architecture? 07:37
- Monoliths, Microservices… Now Cells? Here's What You Need to Know 15:04
- Principles every developer should know (The Twelve-Factor App) 13:59
- What do Multi-Agent Architectures look like? 11:11
- How does Reddit deliver 10.000.000 notifications? #systemdesign 01:10
- Your backend is already obsolete. Here's what's next 10:05
- How to avoid the "Noisy Neighbor" problem in your software architecture? 08:21
- Retry Mechanisms and Patterns in Microservices #Shorts 01:00
- Here’s how Polling can help you with long-running tasks 07:35
- 6 Architecture Anti-Patterns to Avoid 10:06
- Here's what your backend needs for proper Authorization 10:11
- The Power of RabbitMQ Quorum Queues 07:36
- Event Sourcing: Genius or Just Over-Engineering? 15:27
- That's how I would design Uber in 2026 16:19
- Why I stopped relying ONLY on logs (Distributed Tracing) 12:28
- Explaining the obsession over OpenTelemetry... 07:07
- The State of Modern Authentication and Authorization... 12:32
- This is how you protect your backend from a Retry Storm 06:43
- How to run migrations during the app startup? 13:38
- 4 Event-Modeling Mistakes in Event-Driven Architectures 11:15
- What is the difference between Strong and Eventual Consistency? 06:00
- The Secret Weapon Behind Resilient Distributed Systems 12:06
- This architecture will save your system.. here's how 09:30
- Do NOT choose the Event-Driven Architecture unless.. 07:42
