Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create unique collection for each saga state (F.I: using full namespace) #22

Open
oleguerOrtega opened this issue Nov 26, 2015 · 0 comments

Comments

@oleguerOrtega
Copy link

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

@oleguerOrtega oleguerOrtega changed the title Create Create unique collection for each saga state (F.I: using full namespace) Nov 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants