Status

This is not actually part of the text. It is a place where a reader can track the status of the text being completed inside the text itself. This section will not be included in the final text.

Note there are some images used in the text that are not yet licensed. This is due to them possibly changing and will be licensed before the final edition.

• v10 5/4/17 Finish Process Managers. Various editing
• v8 14/2/17 Finish negotiation chapter. Various editing
• v7 9/2/17 Break apart general versioning. Add Behaviour and outside integration versioning, overall considerations, immutable intro
• v6 7/2/17 Add event bankruptcy, atom, other edits
• v5 24/1/17 Add cheating and bunches of editing
• v4 20/1/17 Weak Schema an Copy/Replace started. Some other areas added to + editing
• v3 18/1/17 small changes and release Whoops I did it again
• v2 17/1/17 some small changes and release Simple Type Versioning
• v1 17/1/17 release initial version including Why? and Why not update an event

Goals

The goal of this text is not to discuss Event Sourcing but to discuss how to version Event Sourced systems. The main areas for discussion of versioning are:

• Why?
• Why Not Update and Event?
• Simple Type Based Versioning
• Weak Shema/Hybrid Schema
• Negotiation
• What to do with Mistaken Events
• Copy and Replace models
• Cheating
• Internal vs External
• Versioning of Process Managers

The length of the book is expected to be between 70-100 pages on this subject.

Feedback

Feedback and/or questions on content you feel may not be covered well enough is highly appreciated! If a text has not gone through editing process yet grammar/spelling changes will probably be picked up in the editing process.

Status