bartelink
commented
2 years ago Absolutely go for it - it's great to be able to publicly reference what you are doing when asking questions of the Cosmos team too, as I often do re https://github.com/jet/equinox/tree/master/src/Equinox.CosmosStore etc
Whether or not you get contributors is of course a hit and miss thing - the massive majority will always be people who silently use things. You'll regularly wonder, why am I doing the extra legwork of doing it in public. But over time you'll be glad you did, regardless of that. Sticking it out in a public repo is a good reasoning tool - it can help you figure out the right way to do something in a cleaner fashion than some expedient hack you might do in another context; over time, that yields better solutions and teaches you things.
josdeweger
ealsur
At a client we are currently working on a CosmosDb Migration Runner inspired by Fluent Migrator, since Fluent Migrator does not support NoSql databases. The language is c#, the Target Framework netstandard2.0. Very early stages, not properly battle tested yet. The basic idea is that per collection / document type combination you can migrate documents up to a newer version and down to an older version, as well as renaming collections (which is basically creating a new collection, transferring all the documents, and deleting the old one, since renaming a collection doesn't really exist in CosmosDb). We might introduce transferring documents by document type between collections in the near future as well. All this is achieved by writing migrations as c# classes.
This library brings us the following benefits:
As we are building this, we were wondering if this might be a useful library to open source. Would developers be interested in using this? Since it is very generic functionality, we see no downside in sharing it with the community. For us it's a great way to get feedback and contributions. Looking forward to your feedback!