Database per Service Pattern in Microservices

Build Your Own Redis / DNS / BitTorrent / SQLite - with CodeCrafters.

In the video, I discussed the Database per Service architecture pattern for microservices. Each microservice owning its own database promotes loose coupling and autonomy. The advantages include loosely coupled components, fulfilling specific needs with specialized databases, granular control of scaling, and separate compliance requirements. However, cross-service transactions become complex and costly with this approach. It's crucial to understand the pros and cons of adopting this architecture pattern for optimizing system performance and maintainability.

# Recommended videos and playlists

If you liked this video, you will find the following videos and playlists helpful

# Things you will find amusing

# Other socials

I keep writing and sharing my practical experience and learnings every day, so if you resonate then follow along. I keep it no fluff.

Thank you for watching and supporting! it means a ton.

I am on a mission to bring out the best engineering stories from around the world and make you all fall in
love with engineering. If you resonate with this then follow along, I always keep it no-fluff.

[JatinDholakia]

Great video. Another disadvantage is performing joins across databases. It has to happen on network and increases latency.

[suryansh]

Nice explaination + great visuals u raised the level bro

[abdulmoizsheikh]

Hi. Good stuff. Can you tell why cassandra was chosen for the chat service? Thanks!

[jivanmainali]

So is database per service is like single collection/table for each services?

[jabedzaman]

how do we achieve the thing about relations like my post microservice will have the post and user id and my auth service is having the user table... in short what i want to ask is in monolithic we have a single db so we can use a refrence to user table and post table to avoid making post with user id that doesnt exist... but how to do in a microservice arch??? cause we have seperate db

[jivanmainali]

Is encryption done in db or we have to manage it seperatly?