Please provide the title of the book
.NET Microservices: Architecture for Containerized .NET Applications
What do you think could be improved in this book?
1 - Structure of book has a lot of redundant content. Only need to explain what Docker is and why it is used for Containers once... it seems like every chapter starts off with a repetition about how great Docker is.
2 - Book seems out of sync with code example. In particular missing explanations related to additional packages that are used in example code: grpc, polly, swagger, node.js, indentiyserver4. While there is an entire chapter on "using docker for development" these other packages are ignored. IF the code example needs these packages, they should be included in the book as to why. IF these wont be included in the book, then these should be pulled from the example code... the book should reflect what is in the code and the code should reflect what is in the book.
3 - Design patterns are the key take away for a book on "architecture"; organizationally that would make more sense.
What do you like about this book?
Chapter 3: good discussion on design/architecture choices
Additional context
Book reads like this was written by 10 different people with overlapping subject matter.
Please provide the title of the book .NET Microservices: Architecture for Containerized .NET Applications
What do you think could be improved in this book? 1 - Structure of book has a lot of redundant content. Only need to explain what Docker is and why it is used for Containers once... it seems like every chapter starts off with a repetition about how great Docker is.
2 - Book seems out of sync with code example. In particular missing explanations related to additional packages that are used in example code: grpc, polly, swagger, node.js, indentiyserver4. While there is an entire chapter on "using docker for development" these other packages are ignored. IF the code example needs these packages, they should be included in the book as to why. IF these wont be included in the book, then these should be pulled from the example code... the book should reflect what is in the code and the code should reflect what is in the book.
3 - Design patterns are the key take away for a book on "architecture"; organizationally that would make more sense.
What do you like about this book? Chapter 3: good discussion on design/architecture choices
Additional context Book reads like this was written by 10 different people with overlapping subject matter.