Full description not available
Y**O
Worst Book in my life
I guess no one reviewed this book. Even the author didn't review it.1. Table of contentsTable of contents looks ugly and page number doesn't match actual page number. What is "6" at the end of each line? The total page number is at least 287 in the table of contents but end page of this book is 204.2. Quality of imageThe quality of the images used in this book is bad. I took one of images but it is hard to read the words.The same image is used several times with a bit different description which doesn't make much sense.3. Horrible indentWho can understand this code written here? It is really crazy. It's super hard to find corresponding brace and to understand what's written in a method.4. FontThe exactly the same font is used for both paragraph and code. Sometimes code appears in paragraphs and vice versa. I couldn't recognize it at first glance.It's unbelievably frustrating book but the quality of the used paper and design of the book cover are nice.By the way, I stopped reading this book because nothing stays in my head. At least code MUST be readable.
A**R
Covers the overall benefits, downsides to this pattern and whats its really about
I have been using CQRS for for last year on of the enterprice application and wanted to see others take on this pattern. Most of the approaches described in the book I agree on for some of the problems I think I have better solutins, but I wont go into details in here. I liked the chapter separting the read and write databases and strategies how to tackle them. Because Im not using this approach myself, Because scalability is not really an issue with fixed amount of users, im using what author described as sweet spot, cqrs at the domain model and using sql vendor specific optimization features. Overall im happy with this overview for this price.
A**A
Cqrs (Command Query Responsibility Segregation)
O conteúdo do tema abordado
M**O
Absolutamente desastroso
Absolutamente ilegible. Me pregunto como es posible que alguien sea capaz de publicar un libro en un estado tan lamentable como este. Técnicamente correcto, pero para seguir el código, es poco menos que imposible. Acabas harto, cansado y bastante irritado. El texto se escribe todo seguido, sin puntos aparte, incluso con erratas (el autor no es de habla inglesa y se nota bastante en expresiones erróneas). El código se indenta aleatoreamente, seguir los if anidados o cualquier estructura anidada es una locura, un if se indenta tres veces y el cuerpo de ese if aparece sin indentar, en fin, pérdida de tiempo y dinero.
U**T
Ridiculous excuse for a book.
Aside from the horrid formatting where it looks like someone accidentally moved something in their word file and messed it all up.Every other sentence has some form of grammatical or wording error so that even reading simple, one-line sentences is difficult. Sentences like "Book will answer all these questions and more."Also unformatted code going on for four pages, instead of using diagrams or something.I really dont want to bash the author, because it seems like english might not be his first language and writing a book like that is probably difficult, but that is what publishers and other services are for.
Trustpilot
3 weeks ago
2 months ago