Doubt about aggregate root version about eventsauce HOT 4 CLOSED

Hi @jeffagostinho,

This means you have a concurrency issue. Such issues are out of scope for EventSauce itself but I can help you deal with them if you like. What kind of service layer does you application have? Do you have service classes or a command handling setup? Additionally, what kind of database are you using?

from eventsauce.

Eae @frankdejonge, all right?

This is real, we have the concurrency problem. I ended up identifying when I ran tests on a microservice that we are developing in PHP Swoole using Hyperf, at first I thought it was some detail of this new way to build PHP apps, but I ran some tests on another microservice in Lumen and noticed that we have the same problem

These Lumen microservices run on infra k8s and we are using MongoDB

Thanks for helping

from eventsauce.

I didn't understand the first sentence. What does eae mean?

For concurrency problems you need some kind of concurrency control. Normally in SQL databases you can do a couple of things, like forcing a row lock using SELECT x FOR UPDATE or the GET_LOCK/RELEASE_LOCK functions. You can also use a general purpose mutex on a shared piece of infra like a redlock. The "problem" with the redlock is that your operation could exceed the lock time for long background jobs.

I'm not overly familiar with MongoDB, but from what I remember it does not have locking capabilities that allow you to explicitly lock documents like SQL databases do. So in your case, probably best to implement a general purpose mutex. When you have this in place, you can decorate your service layer or command bus with the locking mechanism to prevent concurrent access to the underlying document.

from eventsauce.

Sorry @frankdejonge, eae would be hey kkk

I understand what you said, I will research more about it. Thank you very much for your availability and congratulations on the project

from eventsauce.