The AWS Well-Architected Framework helps you understand the pros and cons of decisions you make while building systems on AWS. By using the Framework you will learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective systems in the cloud.
Good balance of principles, approaches, and practical techniques
The first part of the book would look boring and too "common sense" without the second part, where you get some practical advice on implementation. Good balance between the two parts, between principles and practical implementation.
This is a very high level summary of aspects you need to pay attention to when designing cloud infrastructure. The text is tightly packed with reference to principles. This also means that the book is very slow to read. This is a more strategic guidance than practical recommendations. If you treat it like that you will get better value from it.
Bullet-point book, written by repetition and spreading out of just a few good ideas
I felt that i needed to finish this book because of how short it is and because I like to finish what I start.
That being said, this book offers very little value. The appendix, which is about 50% of the book is full of copy-pasted content from the chapters. As such, I'd say 25% of the book is literally copy paste. The structure of the book then is based in parts on questions and answers. Most of them go like this: Q: How do you align the system (workloads) to the business goals? A: There are many strategies to ensure alignemt of the workload with the business goals. You must choose from one of these strategies, and implement one that best suites your business and your workload.
So that is just filler text, adds no value.
This book was free, but then I wonder why they even bothered to fill it with so many zero-value paragraphs. They could have easily given us a 10 page description of the framework including some bullet-list of questions, and references to the relevant services, and spare us 75% of the copy-paste and brain-dead repetition.
What's good about the book is that it gives you a high, organisatiom-level view of systems. This is nice. This puts you in the showles of a CTO/CIO. You feel like you're in one of their meetings where they need to decide how to cut costs by optimising parts of the system. That's a nice feeling I got....but then, that meeting turns into total corporate-style BS, boring beyond your wildest dreams, and instead of lasting for w hours, it lasts for a week.
Anyway, I was looking for either examples of AWS architectures, or an organisational view of IT systems... I got both in this book, but presented in a hasty and copy-pasty manner.
Stay away from free books/booklets! Even if they're short, they mess something up in an epic fashion :p
The book describes the overall architecture in simple language and well defined layout, I wish more white papers are available in Kindle format as reading in it is a cool breeze.. Thanks
This whitepaper does a good job at outlining a number of considerations individuals, teams, and organizations must make when designing their systems...particularly if moving to the cloud. The whitepaper is a framework for AWS services, so you must be ready for everything to reference the plethora of Amazon services available. So while a fantastic guidebook for using AWS services and best practices for Amazon cloud-based applications, it also does serve a great reminder of general application practices that we should all be following.
I was hoping for some real life examples of how you can put AWS services together to build working systems. This is really an overview at a very high level
I was expecting to get some specific knowledge. The truth is that the document is a bit too generic for my taste. In fact the Appendix was more interesting for me than the rest of the book. But hey, it's free
Filled with self-evident yet nonetheless practical advice. Would have liked to see some real-world architecture examples but I guess that'd be expecting too much. All in all it's a decent read that can be used as a cheatsheet/reference and that's probably its greatest merit.