[alex-lawrence]

Sorry, there is no printed version at this point. I wanted to focus on the e-book variant first.

While this is not necessarily an argument against a printed version, note that this book works best when reading on a computer. It comes with the full source code bundle and a small utility that allows to execute all code examples interactively.

Also, it is likely that there will be updates to the book in the near future. I'm already considering to write an appendix. By exclusively providing an e-book, iterative improvements are easier to do and the readers get all updates for free.

Nevertheless, I may consider to offer a printed version later on.

[ChicagoDave]

This is an interesting thought. The interactivity and the implementation are actually as important or possibly more important than the book text.

This could lead to a dramatic shift in how technical books are created.

Imagine a new website that didn't offer videos or text or tutorials, but actually was integrated with all of those things together?

So in your case, the book can be read or listened to, as you work on the example implementations. Using a little ML, you could probably even offer suggestions to roadblocks.

Just got sidetracked on this thought.

I'm a DDD guy, but have never personally implemented CQRS and event streams. I love the idea of separate read and write streams, but what is the best mesh of tech to do it well? (rhetorical question)

I'll buy the eBook. Thanks for working on this.

[serial_dev]

It's a good idea to work on the e-book first, iterate and fix most of the issues. However, a printed version would be great (for example, I'm unable to focus while reading on the computer). +1 for the printed version!

[akoncius]

well for that purpose e-readers are good solution - no apps, no notifications, just text what you need :)