Computer Science

Practical Microservices: Build Event-Driven Architectures with Event Sourcing and CQRS

Practical Microservices: Build Event-Driven Architectures with Event Sourcing and CQRS

  • Downloads：2284
  • Type：Epub+TxT+PDF+Mobi
  • Create Date：2021-10-07 09:55:43
  • Update Date：2025-09-07
  • Status：finish
  • Author：Ethan Garofolo
  • ISBN：1680506455
  • Environment：PC/Android/iPhone/iPad/Kindle
  • Download

Download

Reviews

Garrett ，

I want to shout this message from the rooftops: Microservices are a data model， not a deployment strategy！I've seen company after company claim to do "microservices" when it's really just databases behind HTTP servers， and they seem utterly blind to the problems and complexity that comes from that kind of model。 I think the word "microservices" is kind of tainted now， so I appreciated how the author focused on using the term "components" instead （since that word isn't at all overloaded， heh）。 Bu I want to shout this message from the rooftops: Microservices are a data model， not a deployment strategy！I've seen company after company claim to do "microservices" when it's really just databases behind HTTP servers， and they seem utterly blind to the problems and complexity that comes from that kind of model。 I think the word "microservices" is kind of tainted now， so I appreciated how the author focused on using the term "components" instead （since that word isn't at all overloaded， heh）。 But vocabulary aside， I love the kind of thinking that this book encourages。 When I got to the chapter about aggregators I almost cried imagining having to make a single database query to load all the necessary data for a page。 Compare that to a project I'm working on where you have to make at least a half-dozen API calls to load a single page， every single time。 I don't know why anyone thinks that is the right way。Unfortunately I don't know if I'll ever be in a position to promote this kind of architecture at work。 But it's nice to dream。The examples in the book are admittedly a little contrived， but they're more realistic than a todo list。 He tackles some important topics like registration and authentication。 But then other things he says are really important while leaving them as an exercise for the reader。 I don't think after reading this book that I'm fully equipped to go out there and build a full microservice-based system， but at least the book helps me start thinking the right way。 That's something。I wish more people knew about this。 。。。more

Mike Zornek ，

This book was recommended to me as a good introduction to the core concepts of event sourcing design and it delivered。 Awesome read。 Anxious to dig into the sample code and followup with other books / articles。 For me， event sourcing is to MVC as functional programming was to object-oriented programming。 Big （potential） game changer for me。

Ankesh ，

Disappointed with the presentation of the material。

Lebohang Bucibo ，

This book has what looks like a good trajectory into Microservices topics but has a very terrible start that made me give up on the first chapter。 It starts be describing an application built in some Node。JS framework called express。js by simply listing the contents of each of the files of that app with little explanation how they fit together。 I wish it ramped me up correctly so that I advance to the other topics it addresses and which I find relevant to the subject of Microservices。 I sadly sw This book has what looks like a good trajectory into Microservices topics but has a very terrible start that made me give up on the first chapter。 It starts be describing an application built in some Node。JS framework called express。js by simply listing the contents of each of the files of that app with little explanation how they fit together。 I wish it ramped me up correctly so that I advance to the other topics it addresses and which I find relevant to the subject of Microservices。 I sadly switched to a 。Net Core based book because of how it ensured that my transition from one chapter to the next is smooth。 I will not recommend it unless you are proficient in the Express。js framework。 。。。more

Pedro ，

Good practical introduction to Event Sourcing and CQRS， which enabled me to grok the concepts involved。

Renanreismartins ，

The book is a step-by-step "tutorial" and can get quite repetitive。 I would say it could have been a blog series or even some sort of living code session。If you are beginning on the subject， maybe interesting。 But it is definitely something outside the PragProg format。 The book is a step-by-step "tutorial" and can get quite repetitive。 I would say it could have been a blog series or even some sort of living code session。If you are beginning on the subject， maybe interesting。 But it is definitely something outside the PragProg format。 。。。more

Michal Zalecki ，

The book isn't really about microservices。 It's more about the ideas and principles of writing modular software and a good introduction to Event Sourcing and CQRS。 Read the full review。 The book isn't really about microservices。 It's more about the ideas and principles of writing modular software and a good introduction to Event Sourcing and CQRS。 Read the full review。 。。。more

Behrooz ，

Poperly describes the core concepts and points out some common mistakes like using Kafka as message store。However， I won't be choosing microservices architecture for any of my projects until the project becomes so big that tens of developers have to work on the code base。 Even then， won't let them grow out of control （like what happened at Uber）。Just recently， I was unfortunate enough to work on one of these projects that supposedly used microservices architecture but it was one of fake ones tha Poperly describes the core concepts and points out some common mistakes like using Kafka as message store。However， I won't be choosing microservices architecture for any of my projects until the project becomes so big that tens of developers have to work on the code base。 Even then， won't let them grow out of control （like what happened at Uber）。Just recently， I was unfortunate enough to work on one of these projects that supposedly used microservices architecture but it was one of fake ones that is described in the book too。 I ended up replacing Kafka with a simple postgres backed queue for background jobs and merged all of the projects/microservices into a monolith。 End result？ Everybody is happy now from developers to ops。To be clear， I would definitely use what I have learned from this book if I ever develop microservices but the kind of projects that I deal with now do not benefit from it。 。。。more

Sven Kirsimäe ，

What I personally like about this book， is that it does not use de facto tools to show the concepts of event-driven architecture but uses a rather simple low-level stack to present and show the concepts rather well。 For anyone in the industry for some time， it’s definitely not a complex read， a nice conceptual reminder。 Maybe too much of unneeded small-talk and “wow， well done！” for a more mature reader thus， -1 point from there。 Could have saved some amount of pages on that :）

Reference

google book https://www.google.com/search?tbm=bks&q=Practical Microservices: Build Event-Driven Architectures with Event Sourcing and CQRS

hathitrust digital library https://babel.hathitrust.org/cgi/ls?q1=Practical Microservices: Build Event-Driven Architectures with Event Sourcing and CQRS&field1=ocr&a=srchls&ft=ft&lmt=ft

The British Library https://bll01.primo.exlibrisgroup.com/discovery/search?query=any,contains,Practical Microservices: Build Event-Driven Architectures with Event Sourcing and CQRS&tab=LibraryCatalog&search_scope=Not_BL_Suppress&vid=44BL_INST:BLL01&lang=en&offset=0