Why "One Database Per Service" is usually a terrible advice
Try PostHog for free: https://go.fundlevel.co/sdph ======⚡⚡⚡====== Should your microservics share a database or should every microservice has its own dedicated database? This is a question that always sparks a debate. The real correct answer is so obscure that you definitely would not have imagined it. It lies within the Domain-Driven Design and an interesting middle-ground most teams can use. Consider becoming a member of the channel by joining me ❤️ / @softwaredeveloperdiaries ☕ Buy me a coffee: https://www.buymeacoffee.com/software... 🙌 Become my Patreon and get exclusive perks: / softdevdiaries 💼 Follow me on LinkedIn and drop me a message if you'd like: / gadirovgs 💻 Also, let's connect on GitHub: https://github.com/gusgad And don't forget to subscribe for more videos like this 😊

Microservices with Databases can be challenging...

How Instagram Scaled Postgres to 2 Billion Users

Are we really doing this again

Google & AWS Veteran: What Top Tier Software Architects Do Differently

Oskar Dudycz - Event-driven Modelling Anti-Patterns - EventCentric 2025

Deep-Dive into Database Scaling for Millions of Users

The NoSQL Lie That Keeps Developers Overbuilding

Spec-Driven Development: The Fast Track to 10x? - Jerry Nixon - NDC Sydney 2026

Caching challenges that scare even senior engineers

DISCORD Stores 1 TRILLION Messages! Here's How.

Why The Best Engineers Are Solving Code Review Bottlenecks

Spec-Driven Development: AI Assisted Coding Explained

2 Years After Broadcom Destroyed VMware: Where Did Everything Land?

The Modular Monolith: Scale Without Microservices

Message Queues in System Design Interviews w/ Meta Staff Engineer

Why Rust is different, with Alice Ryhl

Here's when Event-Driven Systems should REALLY be used..

Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker

DynamoDB Deep Dive w/ a Ex-Meta Staff Engineer

