Microservices & Data: Implementing the Outbox Pattern with Hibernate
Vložit
- čas přidán 6. 08. 2019
- In this video, I will talk about implementing the outbox pattern with Hibernate.
When you start implementing a microservice architecture, you quickly recognize that managing your data has become much harder than it used to be in a monolithic world. In the past, you used distributed transactions and synchronous communication between different parts of your monolith. In a distributed microservice architecture, this is no longer an option.
If you like this video, please give me your thumbs up and share it with your friends and co-workers.
Like my channel? Subscribe!
➜ bit.ly/2cUsid8
Join the free Member Library:
goo.gl/dtyIIC
Read the accompanying post: thoughts-on-java.org/outbox-p...
Want to connect with me?
Blog: www.thoughts-on-java.org/
Twitter: / thjanssen123
Facebook: / thoughtsonjava
#hibernate #outboxpattern #microservices - Věda a technologie
The explanation of the Transactional Outbox pattern is pretty nice and clear, as for me. Thank you! :)
very clear articulation. thanks for this!
Nice explanation. I just implemented absolutely the same, for the same reasons, without knowing that this is a formalized design pattern.
Fascinating topic! I find I am becoming more of a persistence nut than anything else these days, that probably has something to do with your videos :)
Happy to hear that :)
Wonderful overview explanation. Your teaching methodology is unique and didact.
Thanks!
Nice, thanks very much.
And about the concurrency of many microservices instances reading and writing in outbox table? Should I use a lock?
What about the message order, it's not important?
Won't be interesting to have a timestamp column and store the date and time which the message was created? So it can be sent in order later? Or even use a sequential id.
Thank you for nice video. Can you make a video for inbox pattern?
How could I manage transactions when I have more than one instance of the same persistence microservice?
You can use local transactions in the same way as you would use them in a monolithic application.
Local transactions don't cause any problems in a micorservice system.
What about gRPC?