Building Micro-Frontends: Scaling Teams and Projects Empowering Developers

I was pleasantly surprised by just how relevant the content of this book has held up given an industry where accepted practices change seemingly month-to-month; the design patterns and insight within are impressivley valuable and written in such a way that they're applicable generally, regardless of your working context.The author makes a solid case for micro-frontend architecture and the high level conceptual overviews are convincing I'd like to have seen more consideration given to the down sides and I think some of the advice, specifically around build and deployment is questionable.

I pre-ordered this book as soon as I saw it was coming, and I was really looking forward to it. Unfortunately, it's turned out to be a huge disappointment. I just can't recommend buying it.I have 3 problems with this book:1) I've now learned that the O'Reilly "Building..." book series are poorly named. This book, along with Building Microservices (Sam Newman) both have the same problem of being almost entirely just anecdotes, opinions, and advice - without ever actually showing you how to _build_ anything. They go on and on about what you should do, but they never tell you _how_ to do it (hands on implementation). This book does point you to a code repo, but there's almost no code in the book. So find a better name, O'Reilly.2) The author assumes the reader has a _vast_ amount of background knowledge, from every tier of full-stack development, to an understanding of CDNs and AWS (Lamda, S3, etc.), to complex aspects of React (such as Routing, Context, SSR, etc.)/JS/DOM, to authentication and JWT, and a whole lot more. Oh, and you also better be very comfortable with microservices architecture and Domain Driven Design (DDD).The problem is that if you _do_ know all that stuff (which I pretty much do), this book offers very little new additional value. Much of what he covers ends up being pretty obvious. If you don't, you'll have no idea what he's talking about when he casually refers to various technologies or patterns with zero background introduction, like you've used them for years.3) Even if you DO cover #2 well, for the things that aren't obvious, the writing is just plain confusing and hard to follow. The author moves so quickly at times that if you are missing a piece or 2 of what he's saying it makes no sense at all. Other times he says a lot and it's all quite clear, but it doesn't add up to much. On average, he just doesn't explain things methodically or clearly in an additive fashion, as Sam Newman does manage to achieve in his writing on similar topics.Finally, just a personal nit – most of the pattern or flow diagrams in the book are upside down, imho. For example, the diagrams that explain anything full-stack have the database at the top, and the API and/or client (browser, device, etc.) at the bottom. It's just ... weird.All of those complaints aside, this book does explain a few things I didn't know before, and it does refer to some handy tools, frameworks, libraries, and other books for further reference. I gave it 2 stars because it does have some genuine value to offer. It's just too bad that the confusing writing and poor signal/noise ratio make the good stuff so hard to find and understand.

I think is too much theory, maybe you must include some exercises like every book of programming

I have been working with Micro-Frontends for the past couple of years on a large enterprise application and found this book to be really helpful. This book talks about 4 decisions that should be made before developing a Micro-Frontend and talks about the reasons why you would want to build an application using Micro-Frontends. At the end of the book, Luca interviews different companies that are using Micro-Frontends and they discuss the pros/cons and issues they may have run into while implementing Micro-Frontends. I really liked this book because it was not about coding or implementing front-end code for Micro-Frontends, it was more about the technology/business decisions you need to make while developing Micro-Frontends.

I was afraid that the book would come in bad condition, however it turned to be in pretty good shape. Would buy again

for people who works on big project to scale in right way, with many practical case from biggest tech companies

This book is well designed and covers different business layers