You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To be able to use a single mongoDB database to store the persistence of all or different NSB services. It would be goo to make sure every service state is stored into separate collection. So no possible collusion of two different states situation could arise.
Now if two different services uses the same state name (f.i. OrderState) and same identifier, which is probable(f.i. OrderId). we can be hit by issues of loading or modifying different states.
To solve this we might use full namespace to identify saga collections.
Also we could set up a prefix per service that could be use to prefix all states into the service (if full namespace is too long)
By having this we could reduce the admin tasks. As if you are embracing a microservices architecture soon you'll have quite a lot of services which might have it's own repository plus the persistence DB in mongo. That will create a lot of different similar DB in mongoDB to look after.
To be able to use a single mongoDB database to store the persistence of all or different NSB services. It would be goo to make sure every service state is stored into separate collection. So no possible collusion of two different states situation could arise.
Now if two different services uses the same state name (f.i. OrderState) and same identifier, which is probable(f.i. OrderId). we can be hit by issues of loading or modifying different states.
To solve this we might use full namespace to identify saga collections.
Also we could set up a prefix per service that could be use to prefix all states into the service (if full namespace is too long)
By having this we could reduce the admin tasks. As if you are embracing a microservices architecture soon you'll have quite a lot of services which might have it's own repository plus the persistence DB in mongo. That will create a lot of different similar DB in mongoDB to look after.
Related to this topic:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/particularsoftware/V99-0Rjq8Fk/v6PNb1SdBAAJ
The text was updated successfully, but these errors were encountered: