We are using C# driver in .netcore. We are looking for sound implementation of Document Versioning similar to SQL Server versioning. I have gone through BlogPost where they discuss document versioning.
Thanks
We are using C# driver in .netcore. We are looking for sound implementation of Document Versioning similar to SQL Server versioning. I have gone through BlogPost where they discuss document versioning.
Thanks
Document versioning in MongoDB can be implemented in multiple ways, each with its pros and cons. Here are a few options:
Whichever method you choose, make sure to test it thoroughly and to consider the trade-off between the complexity of the solution and the requirements for versioning in your use case.
Does the process which reads Change Stream have to be running consciously or it can have downtime? Is there the concept of “resume from” when I start reading from ChangeStream again? What are the provisions for consistency in this?
I was also thinking about implementing versioning in my application itself with the below approach.
Below operations would be in the transaction
Insert for the document (newDocument) comes in with PrimaryKey = PolicytId
What do you think about this approach?
Hi @Marmik_Shah
There are a couple of blog posts that may be useful to you regarding this topic:
Note that those two posts are quite technical, but contains a lot of interesting information regarding the pros/cons of some approaches. Those are a bit old, but still relevant today since it deals with schema design.
Best regards
Kevin
Thanks for the links.
See