Cloud fullstack engineer based in Austria

At the date of writing this, the second edition (and a very different book from the first edition) of *Serverless Architectures on AWS* has been around for less than six months, and there are hardly any reviews about this to be found. Therefore, this post summarizes the book parts of the book and presents what I liked and disliked about the chapter. In the end, I will give a short verdict on the book.

AWS currently offers over 200 different fully-featured services, but not all of them are serverless. How can we tell whether a service is serverless or not?

In this post, we'll have a look at a resource-intensive application that was initially written in a monolithic fashion, how the system was migrated to cloud-native architecture and what benefits this provides.