Domain Storytelling: A Collaborative, Visual, and Agile Way to Build Domain-Driven Software (Addison-Wesley Signature Series (Vernon))

Describes a iterative design process for eliciting requirements, modelling, designing and documenting APIs. Considerations for security and application of current best practices around API Gateways, OAuth and OpenID Connect. Good primer on microservices but perhaps would've been better as an Appendix like the HTTP primer. Some errors in figure numbers and proofing.

What I liked: - Easy-to-follow process on how to use domain storytelling - Great recommendations for analog and digital approaches - Relatable examples and stories to showcase how to use it - Clear examples on why not to approach it in certain manners What I didn't like: - Got the printed copy and the pages were thin. Sometimes the diagrams and words from the previous page could be seen just enough that it was distracting. (The attached photo is from p. 49.) If there's a digital-only version of this, I would rate this 5 stars for content. I am looking forward to adding Domain Storytelling to the practices I employ with my clients and projects.

Si eres de IT y te toca diagramar Bounded Context, este es tu libro de caberera. No deberías separarte de él.

The information in the book is practical and useful as a methodology for recording stakeholders' workflow stories. A lot of it is "common sense," but it's helpful to have a shared language and a "source" to point to in order to get people on the same page. The bigger issue with the book is physical quality. Many of the pages are stuck together, either uncut or inadvertently glued. There is also an almost entirely empty signature at the end of the book -- eight pages or so that are completely blank. There are diagrams with "color" elements that are presented as simply 70% gray, rather than having outlines or symbols. All of these speak to a very poor design and production process, and is a disappointment for what I expect from the "Addison-Wesley Signature Series." PoEAA this ain't.

For anybody with some architecture background it’s just too wordy. The insight to page ratio is quite low. I’d pay the same for half of the pages or even for a quarter. The technique itself is great and I’m happy to read about it. It’s how the book is written that I dislike. The book might make sense as the very first encounter with modern architecture. But for that the topic is too niche and new, at least today. I wouldn’t recommend it to newbies, there are books that cover fundamentals better.