I was wondering how you folks are managing your event store objects, like projections and persistent subscriptions and things, as they evolve? My goal is to have artifacts in source control that can the automated release process can use create/update the ES changes needed for a given release. Anyone have this worked out?
Thanks,
Nathan
I generally have an sh script that adds projections which helps a lot when clearing an event store out and starting again. This is kept in a version control system to track changes.
Hope this helps…
Kind regards,
Mark
Thanks Mark. That approach might be good enough for now. If anyone ever writes an ES “migration” library for .NET let me know 