Serverless Architectures on AWS

by Peter Sbarski, Yan Cui, Ajay Nair

Design low-maintenance systems using pre-built cloud services! Bring down costs, automate time-consuming ops tasks, and scale on demand.

In Serverless Architectures on AWS, Second Edition you will

First steps with serverless computing
The principles of serverless design
Important patterns and architectures
How successfully companies have implemented serverless
Real-world architectures and their tradeoffs

Serverless Architectures on AWS, Second Edition teaches you how to design serverless systems. You’ll discover the principles behind serverless architectures, and explore real-world case studies where companies used serverless architectures for their products. You won’t just master the technical essentials—the book contains extensive coverage of balancing tradeoffs and making essential technical decisions. This new edition has been fully updated with new chapters covering current best practice, example architectures, and full coverage of the latest changes to AWS.

Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.

About the technology
Maintaining server hardware and software can cost a lot of time and money. Unlike traditional data center infrastructure, serverless architectures offload core tasks like data storage and hardware management to pre-built cloud services. Better yet, you can combine your own custom AWS Lambda functions with other serverless services to create features that automatically start and scale on demand, reduce hosting cost, and simplify maintenance.

About the book
In Serverless Architectures with AWS, Second Edition you’ll learn how to design serverless systems using Lambda and other services on the AWS platform. You’ll explore event-driven computing and discover how others have used serverless designs successfully. This new edition offers real-world use cases and practical insights from several large-scale serverless systems. Chapters on innovative serverless design patterns and architectures will help you become a complete cloud professional.

What's inside

First steps with serverless computing
The principles of serverless design
Important patterns and architectures
Real-world architectures and their tradeoffs

About the reader
For server-side and full-stack software developers.

About the author
Peter Sbarski is VP of Education and Research at A Cloud Guru. Yan Cui is an independent AWS consultant and educator. Ajay Nair is one of the founding members of the AWS Lambda team.

Table of Contents
PART 1 FIRST STEPS
1 Going serverless
2 First steps to serverless
3 Architectures and patterns
PART 2 USE CASES
4 Architecture highlights, lessons learned
5 A Cloud Architecture highlights, lessons learned
6 Architecture highlights, lessons learned
PART 3 PRACTICUM
7 Building a scheduling service for ad hoc tasks
8 Architecting serverless parallel computing
9 Code Developer University
PART 4 THE FUTURE
10 Blackbelt Lambda
11 Emerging practices

Genres: Computer Science, Software, Technical, Architecture, Programming, Technology, Nonfiction

256 pages, Paperback

Published April 7, 2020

Reviews

[Gourav Sengupta · Rating 5 out of 5]

This book takes you back to the days when authors used to write books to express and share the perfection, joy, achievement and excitement of doing something beautiful. You learn both the semantics and the syntax. You learn to see things and develop the reasoning behind what is right, and why it is so. And you learn it by walking the path.

This book simply puts back the joy of reading a technical book.

[Andrei Barbu · Rating 2 out of 5]

Leaves out all of the hard parts around security, monitoring, long-term maintenance, zero-downtime refactoring, etc. all while building a trivial app. The use of some random non-AWS services for core functionality like Auth0 instead of Cognito is particularly grating and disappointing.

[Ane · Rating 4 out of 5]

Very insightful and complete overview of the serverless architectures on AWS.

[Elie De Brauwer · Rating 4 out of 5]

As cloud providers like AWS are moving forward extremely fast it is also extremely difficult to find any up to date information/reading material other than the online docs. This book clearly shows that it is possible to come up with a decent work on such a fast moving topic. I mainly used the book as a refresher for earlier knowledge and to broaden my knowledge on the topic and the book served both purposes very well. I must however admit that I choose not to go through the entire use-case of the book, I understand why the other did it, but if you focus is mainly on certain topics then more standalone example would be more worthwhile.

[Hasse · Rating 3 out of 5]

I think there should be some more concrete examples where you could gain some practices

I also don’t agree on “misusing DynamoDB” for a cron like service. This only adds complexity especially in the long run. The idea with serverless in my opinion is to simplify usage. So using services for something they are not designed for is the wrong way to go

The comparison with terraform to other tools is flawed. Terraform have had modules for a long time which can be used just as you can use constructs with cdk. Also the praised rollback function cloudformation has is not always working (especially if you ci/cd role doesn’t have the right permissions). I have multiple times seen cloudformation stacks come in a state where the only solution is to delete the stack which I think is unfit for production

Yes terraform doesn’t rollback (it is declarative) so the rollback is to rollback your code and apply again. So I think the comparison is unfair

Also I wouldn’t myself deploy infrastructure and application with the same pipeline/tool as the lifecycles of infrastructure and application is often not the same(so I would not deploy update to lambda code with the infrastructure pipeline)

[Sebastian Sanio · Rating 5 out of 5]

I am working with serverless on AWS since a year ago and I have two certifications (architect associate and developer associate).

I learned a few things from this book, particularly about Auth0 as an alternative to Cognito, Firebase and some good practices regarding architecture at a high level.
The rest is in line with what I've already been doing, I would have probably learned it faster if I had read this book before, so I recommended it to serverless beginners and also to more advanced developers.

[Ruslan · Rating 4 out of 5]

There is some useful information in the book, such as real-world serverless use cases overview (though a bit artifical and not in scale enough) and some introductory concepts. Apart from that, the book is slightly too optimistic about serverless, missing important FaaS challenges. I would like to see more technical FaaS definition.

[Sheen Brisals · Rating 5 out of 5]

One of the best technical books that I've read recently. With clear explanation and well laid out hands-on example, the author has managed to present the topic and the AWS ecosystem in such a way to suit all types of readers.

[Héctor Rodríguez · Rating 4 out of 5]

Really good book, but I would only advise it to beginners. The architecture part is a bit intermediate and quite interesting, that's true, but overall its a hands on practice on how to build an fairly simple architecture

[Frank Palardy · Rating 4 out of 5]

Good but detailed and the details are likely to change.

[Gernot · Rating 5 out of 5]

The most up to date and comprehensive book on this topic. acloudguru is a knowledge leader (if this word exists)

[Igor · Rating 4 out of 5]

Great explanations and examples. I'd like if it had C# examples as well. Some things are a little bit changed since the book was written, but it's still very useful.

[Babak Ghadiri · Rating 4 out of 5]

https://www.youtube.com/watch?v=LAWjd...

[Eric Li · Rating 5 out of 5]

informative.

[Frank · Rating 4 out of 5]

read this for a work project.

[Matt · Rating 4 out of 5]

Nothing stunningly original that you can't find on blogs etc but it is well written and well put together.

[Jinay Shah · Rating 4 out of 5]

One star less because it should have been triple the length it has right now. I’m hunting for content on this topic but this book seems to be the only one out there.

[Héctor Iván Patricio Moreno · Rating 5 out of 5]

Este es uno de los libros técnicos más interesantes que he leído en los últimos años, tal vez porque presenta una perspectiva que nunca había analizado y con la que no estoy familiarizado. Me gustó mucho además la forma en la que tratan los problemas, en la que se enfocan en el fondo de los asuntos y no solamente en las herramientas, además de que analizan los problemas que presentan desde diferentes puntos de vista y desde diferentes soluciones, dejando claro que siempre hay intercambios de valor entre los diferentes diseños.

Lo consideraría más un libro de arquitectura en general, enfocada en arquitecturas de microservicios. El punto acerca de AWS es que describe los servicios que cumplen con los requerimientos funcionales y no funcionales y, mejor aún, te ayuda a entender más profundamente por qué un servicio es mejor que otro para diferentes casos de uso.

También tiene una guía de optimización de Lambda y sobre prácticas emergentes en este tipo de arquitecturas, que considero muy útiles para empezar.

Finalmente, tiene un análisis de los diferentes frameworks para poder realizar de mejor manera estas implementaciones, que considero muy muy útil para evaluar cómo podemos empezar un proyecto.

Me quedo con varias cosas más allá de las herramientas acerca del libro:

- No es necesario seguir la ideas tradicionales sobre arquitectura de software siempre, mucho menos ahora que tenemos servicios completamente administrados (serverless)
- Con este tipo de servicios podemos construir productos de manera más eficiente
- Tenemos que buscar trabajar el mayor tiempo posible en las cosas que diferencian nuestro producto y contratar o comprar las no diferenciadas
- Las arquitecturas de microservicios requieren maneras de pensar completamente nuevas
- Para evaluar una arquitectura, tenemos que definir los requerimientos funcionales y no funcionales por adelantado para no sesgarnos por nuestra solución favorita al momento de evaluar
- Para llegar a una solución efectiva conviene evaluar diferentes arquitecturas contra nuestra matriz de requerimientos previamente priorizada

Lo recomiendo mucho a todos los arquitectos y desarrolladores de software que quieren avanzar en su carrera.

[Railgun · Rating 4 out of 5]

Practical book. And in the end, you get a working serverless web app which is great!

[Rebecca · Rating 2 out of 5]

Honestly very underwhelming. Mostly just a random stream of words. The definition of serverless is shifting throughout the book, the editing is poor, the examples mainly about architecture/microservices and IaC, and not really providing anything on the specific serverless aspects of it.

The only interesting part was the one on comparing different products for different kinds of performance requirements, and seeing how this might impact the non-functional performance of a product you are building. Other than that I barely remember what the book was even about...