Software Architecture Patterns for Serverless Systems: Architecting for innovation with event-driven microservices and micro frontends

I was always curious about serverless but didn't know where to start. I heard about this book and I gave it a read. It was great to give me the information I needed to understand serverless. I'm usually a person that steers away from it, but thanks to this book, I will consider to use serverless in my future projects.

Much of my review stems from my background: I've been in software development for 25 years running and I'm involved with maintaining and evolving legacy monolithic systems. So I've gone through a good chunk of the history pretty much - from client-server, to web-based and now to cloud-native systems. Suffice to say I'm always in the lookout for material that shows the state-of-the-art and how systems are being designed, developed, tested and operationalized currently.It is rare to find a book that not just explains what or how an architecture is to be implemented but also the why. It is truly insightful to know how much of the pitfalls of the engineering trends and decisions made before have contributed to where we are today. People my age - who have done their share of development and might either be working as managers, enterprise architects, or department leaders - need to appreciate how critical it is for current systems to be designed to adapt to change (as cliche as that sounds) and how necessary the mindset is of architecting systems with change and speed as the driving principle. This book does an outstanding job of setting the reader's mindset by showing the whys through a walkthrough on the barriers that prevent us from shipping software fast and responsive to change.While the book presents the current approach (or one of possible approaches) in designing software, it doesn't shoehorn that down to the reader's throat and has actually presented the potential pitfalls of modern design (i.e. the microservices Death Star). This has been particularly refreshing for me to hear since all we hear about currently is how microservices is the way forward from monolithic and the Holy Grail of solving all of our development issues.I recommend this book for those who want an overview of modern software architecture design with a focus on serverless, with a sound exposition on how we got here and the reasons for doing so. It's difficult to find this kind of information out there as most jump immediately to implementation details.

As a software systems architect, there is a lot to wrap your head around when considering serverless. I've been designing and fixing software systems for 20+ years, but I had not done a deep dive into serverless until reading this book.The book explains why serverless is important today, details the principles & objectives of a serverless architecture, and provides a practical catalog of useful architectural patterns (even if you're not implementing a purely serverless approach).I've already applied several concepts to my current projects, and look forward to implementing several more as I build.I highly recommend for architects and engineers who want to understand serverless better and add serverless approaches to their tool chest.

Software Architecture Patterns for Serverless Systems presents a detailed guide for software architects and aspiring architects venturing into the realm of modern software design. By emphasizing serverless systems managed by highly decoupled teams with complete ownership over each system's components connected through event bridges in an event-driven fashion, this book offers actionable insights and strategies crucial for success in today's fast-paced landscape. I really liked the mindset of "architecting for innovation" and "architecting to change" since products evolve and we need to iterate as fast as our products. The author's expertise shines, rendering this book essential for those aiming to construct robust, scalable, and inventive systems. Now, the book is well structured and each chapter states very well its relation to others, you can navigate between chapters to recall important content, I think this is a plus that makes the book more reader friendly.

Great high level descriptions of patterns, as well as actionable examples and details throughout the book. This book is a thorough how-to resource for serverless first as the go-to architecture for your next cloud solution. From the high level to the most detailed, this covers the design patterns you will see repeated throughout the industry. Need to pick this up as a resource for any developer.

What a fantastic book. I've been designing, implementing, and managing distributed systems for years yet learned a great amount from this book. The chapters flow well making it easy to follow along with each section packed full of examples and clear explanations. The accompanying code samples are thorough and elegantly implemented. All around this was an excellent book. I strongly recommend this to anyone with any level of experience.

I can solidly recommend this book!I liked how the book takes a cohesion approach to not only the technology itself, but the design patterns and wider SDLC that should be considered to deliver a complete solution. You can see the author is aware of evidence-based approaches to process (i.e. Forsgren, Humble, Kim), where evidence can be shown to produce positive results from process -- as opposed to the cargo-cult variety of process selection we see so much of today. I also appreciated how they went in-depth into the steps needed for a complete solution (i.e. not only your standard front end to bank end dissection, but also scaling, decoupling, multi-region, intersystems concerns, events, observability, etc).

This book is both an excellent intro into the world of serverless computing in the cloud, as well as a guide for experienced engineers who are attempting to modernize their stack. It’s a good reference with easy to find sections written in a way that’s not condescending to the technically minded.