Microservices with Databases can be challenging...

======⚡⚡⚡======

Here are 5 microservice patterns that can facilitate working with databases. Among them: Saga patter, CQRS, Even Sourcing, as well as other useful theory on database transactions and Event-Driven Architecture.

📚 Resources:

And don't forget to subscribe for more videos like this 😊

[karankhaira]

Fantastic video! I especially liked you mentioning anti patterns. They helped a lot with understanding the concepts

[TheSadilek]

Learned a lot and it helped me relax on a Friday night. Thanks man

[VitalMercenary]

Thank you for this video. I really enjoyed it!

[andydataguy]

This is so useful! Needed done help untangling spaghetti and now I've got a deeper understanding of these tools

[achrefnabil]

Bro can you make mern stack project with DDD clean architecture Cqrs event sourcing

[sauravkumarsharma]

I have one doubt also when to use kafka and when rabbitmq i read some where kafka is log base and rabbit mq is in memory..????

[sanjeevsjk]

Superb Video. I would like to see practical samples of what we discussed here

[yoloopen]

Shared db shouldn't be called an anti-pattern. Becasue if you have a split payments and users dbs, you'll still have some dependencies between them, and you're complicating your life drastically by rolling out a multi-db transaction, it's super error prone. So multi-db schema hard to get right and hard to maintain.Deadlocks doesn't seem to be a relevant argument, because if you're updating tables that aren't related there cannot be a deadlock. And if you're updating user and a payment simultaneously, you can run into a deadlock condition either with a shared db, or during your multi-db transaction. 3:00 "If you're trying to scale in the future" - valid point, but "in the future" is the key here. If you'll have to scale it in the future, you'll be dealing with more problems of multi-db transactions in the future, rather than from the beginning.

And watching further only assured how error-prone distributed transactions are. "1 phase: we begin and do inserts, 2 phase we do the commit" - no, this is wrong, it will be screwed up if your "commit" query fails in the second phase, this is not what 2 phase is. And this is the exact reason why everybody should avoid designing multi-db microservices at all costs without necessity, and do a thorough research if there is a necessity.

"And a second pattern is Saga, but rollback here is too complicated for explanation, so let's move further, but remember that the simple way is an anti-pattern"

[diwakarisonyoutube]

I'm so early that higher resolution is just not available yet.

[tesla]

Can we say that CQRS is similar to setting up read replica. Where there ia a master and multiple read slaves

[emonymph]

Liked and subbed you have a cute voice btw, love it.

two questions.
1) with CQRS if we're having a write and read DB. can we just use normalized OLTP for write and denormalized OLAP for read? Like why not read from OLAP if its faster at that.
2) same with streamed (kafka) event log. why don't we make the read DB from kafka a OLAP or event-stream processor like flink?

please correct me where my thinking is wrong.

[sauravkumarsharma]

hello sir this is best explanation video . i was send connection request linkdin please accept

[gourabsarker]

Sir do you earn 100k euros a year as a software engineer? Plz reply. Thanks a lot.

[wag]

Better architecture or you mean a lot money to spend