The book covers the following phases:
I really appreciated the section on API gateways and service meshes, which I found very well explained. This book is an excellent approach to mastering API design.
I learnt a lot of things and I took a lot of notes so I thing it is a very useful book. It covers a lot of topics about data format, transactions and it explains everything with details.
The book covers all areas of architecture, opening a door to quantum computing in this 4th edition. I imagine this is meant to give the work a more contemporary touch, but I find its format rather tedious. Despite the title, it really lacks a practical aspect—there are open doors, but little substance, in my opinion….
This book was very comprehensive, but it is now outdated. Some concepts are still interesting, but they are now better developed elsewhere, such as in Designing Data-Intensive Applications , while others have become obsolete. This reminds us that no matter the value of a book or its author, technology evolves so fast that 20 years feels…
The first chapter, or even the first two chapters, of this book are very interesting from my point of view. However, as it progresses, it loses steam because the author essentially keeps repeating that one must account for the ‘multi-tenant’ constraint everywhere. In summary, you either vertically split each layer so that each separation corresponds…
One of a the best book about Solution Architecture AWS oriented. AWS Solution Architect Handbook 1. Core Concepts Global Infrastructure: Regions, Availability Zones (AZs), Edge Locations. Shared Responsibility Model: AWS → Security of the cloud (infra, services). Customer → Security in the cloud (data, IAM, configs). Well-Architected Framework → 6 Pillars: Operational Excellence Security Reliability…
It was not a big experience. This book is a little boring , and there are a lot of code, it is not very useful.