Serverless Architectures on AWS, Second Edition

Well written, easy-flowing information. Enjoyed the introduction, overview, and real-world use cases. The final section of the book (Black Belt Lambda and Emerging Practices) was my favorite. Learned a lot! Read this book cover to cover, including the appendices. Highly recommended purchase!

In this book the author has laid out the details of Serverless computing effortlessly. He has described every aspect of Serverless computing and what it takes for an application to become Serverless. In the first three chapters, the author has described Serverless architectures for a layman followed by in depth analysis of the Architectures of "Yle" (social media site), "acloudguru"(website that teaches online students). In the last two chapters the author has described the pre-requisites and the detaiks for implementing a SQS, and how to transcribe a video file (break it into smaller segments, separate the audio then merge the files in a binary tree format) to get the final video with the contents merged appropriately. The things I liked about this book 1. Content is easily understandable. 2. Examples drive the way to understand the architecture better. Include videos for better explanation. Overall, great read to learn about Serverless on AWS.

AWS can be a whirling dervish of expanding services and new features for professionals and people just starting their careers. So let's break this down to a simple question. Why is this book worth your money and lifetime? The book provides accessible hands on updates to the labs/workshops from the first edition and has expanded architectural analysis of different implementations and lessons learned. If you are completely unfamiliar or lightly familiar with the subject matter, the labs/workshops will give you the hands on ability to both engage the material and consider directions and design choices made by others in a tone that does not come off as 'carved in stone'. But wait you say, I'm an experienced professional! What more do I have to learn? Go back to my opening statement, AWS is constantly changing and the book provides experienced views of implementations and lessons learned, sometimes we can avoid a mistake by learning about how others thoughtfully made it. What is the book missing? It would have been great to have additional detail or an appendix regarding metrics and key points of interest that were being tracked which led to architecture and implementation shifts in the use cases. What was done and how would the authors approach the same architecture/engineering issues today? Expanding cost analysis in appendix B, I understand that cost analysis is really dry material but a critical factor of success is understanding cost patterns and building muscle to recognize and remediate inefficiencies. I enjoyed this book so much, I even bought access to the 2ed edition when it was a work in progress at Manning. The updated labs/workshops helped to enforce the concepts and ideas, I still consider the material both educational and even entertaining. Peter's work was quite good in the first edition, inputs from Yan and Ajay seem to have made the second edition even better. I hope this review helps and with you the best of luck.

One of the troubles with learning system architecture is that one is exposed to a limited number at work, and the architectures you can imagine and implement yourself. I loved reading through these architectures and getting exposed to ideas that I'm not already exposed to. Also, I generally love to have a hard-copy book so I can continue my learning when I'm away from my computer -- and I love getting away from my computer. I especially like trying to rate the architectures based on fitness criteria. Great practice. Thank you, authors.

Sin duda alguna, aprenderas de Serverless con este libro. Expone al lector los patrones mas utilizados. Sin embargo queda un poco corto para quien busque un poco de guia con respecto a REST API's Considera que no es necesario tener un conocimiento basto de AWS pero sin duda alguna te ayudara un poco el saber de los servicios mas utilizados como SNS, SQS, Lambda, S3, etc. El lenguaje del libro utilizado para los ejemplos en JavaScript, pero es bastante facil traducirlo a otros lenguajes.