Peter Sbarski-Serverless Architectures on AWS. With examples using AWS Lambda-Manning Publications (2017)

Ferguson xii preface xv acknowledgments xvii about this book xix about the author xxi about the cover xxii P ART 1 F IRST STEPS ...1 1 Going serverless 3 1.1 How we got to where we are 4

Serverless Architectures

on AWS

PETER SBARSKI

with Forewords by Patrick Debois

and Donald F Ferguson

M A N N I N G

SHELTER ISLAND

www.manning.com The publisher offers discounts on this book when ordered in quantity For more information, please contact

Special Sales Department

Manning Publications Co

20 Baldwin Road

PO Box 761

Shelter Island, NY 11964

Email: orders@manning.com

©2017 by Manning Publications Co All rights reserved

No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks Where those designations appear in the book, and Manning

Publications was aware of a trademark claim, the designations have been printed in initial caps

Manning Publications Co Development editor: Toni Arritola

20 Baldwin Road Technical development editor: Kostas Passadis

PO Box 761 Project editors: Kevin Sullivan and Janet VailShelter Island, NY 11964 Copyeditor: Linda Recktenwald

Proofreader: Melody DolabTechnical proofreader: David Fombella Pombal

Typesetter: Dottie MarsicoCover designer: Marija Tudor

ISBN 9781617293825

Printed in the United States of America

1 2 3 4 5 6 7 8 9 10 – EBM – 22 21 20 19 18 17

who always supported and encouraged my passion

for computing

contents

foreword by Patrick Debois xi foreword by Dr Donald F Ferguson xii preface xv

acknowledgments xvii about this book xix about the author xxi about the cover xxii

P ART 1 F IRST STEPS 1

1 Going serverless 3

1.1 How we got to where we are 4

Service-oriented architecture and microservices 6 Software design 7

1.2 Principles of serverless architectures 9

Use a compute service to execute code on demand 9 Write single-purpose stateless functions 10 ■ Design push-based, event-driven pipelines 10 ■ Create thicker, more powerful front ends 10 ■ Embrace third-party services 12

1.3 Transitioning from a server to services 12 1.4 Serverless pros and cons 12

Decision drivers 12 ■ When to use serverless 14

1.5 Summary 15

2 Architectures and patterns 16

2.1 Use cases 16

Application back end 17 ■ Data processing and manipulation 17 ■ Real-time analytics 18 ■ Legacy API proxy 18 ■ Scheduled services 18 ■ Bots and skills 19

3.2 Configuring Simple Notification Service 54

Connecting SNS to S3 54 ■ Getting email from SNS 57 Testing SNS 57

3.3 Setting video permissions 57

Creating the second function 57 ■ Configuring and securing 58 ■ Testing the second function 59

3.4 Generating metadata 60

Creating the third function and FFprobe 60

3.5 Finishing touches 63 3.6 Exercises 64

3.7 Summary 65

4 Setting up your cloud 66

4.1 Security model and identity management 67

Creating and managing IAM users 67 ■ Creating groups 70 Creating roles 73 ■ Resources 74 ■ Permissions and policies 74

4.2 Logging and alerting 76

Setting up logging 77 ■ Log retention 78 ■ Filters, metrics, and alarms 78 ■ Searching log data 80 ■ S3 and logging 80 More on alarms 81 ■ CloudTrail 85

4.3 Costs 87

Creating billing alerts 87 ■ Monitoring and optimizing costs 88 ■ Using the Simple Monthly Calculator 89 Calculating Lambda and API Gateway costs 90

4.4 Exercises 92 4.5 Summary 93

P ART 2 C ORE I DEAS 95

5 Authentication and authorization 97

5.1 Authentication in a serverless environment 98

A serverless approach 98 ■ Amazon Cognito 100 ■ Auth0 101

5.2 Adding authentication to 24-Hour Video 102

The plan 102 ■ Invoking Lambda directly 104 24-Hour Video website 104 ■ Auth0 configuration 106 Adding Auth0 to the website 108 ■ Testing Auth0 integration 113

5.3 Integration with AWS 114

User profile Lambda 115 ■ API Gateway 118 Mappings 121 ■ Invoking Lambda via API Gateway 124 ■ Custom authorizer 125

5.4 Delegation tokens 129

Real-world examples 130 ■ Provisioning delegation tokens 130

5.5 Exercises 130 5.6 Summary 131

6 Lambda the orchestrator 133

6.1 Inside Lambda 133

Event models and sources 134 ■ Push and pull event models 135 ■ Concurrent executions 136 ■ Container reuse 137 ■ Cold and warm Lambda 137

6.2 Programming model 139

Function handler 139 ■ Event object 139 ■ Context object 140 ■ Callback function 141 ■ Logging 142

6.3 Versioning, aliases, and environment variables 142

Versioning 142 ■ Aliases 144 ■ Environment variables 146

6.4 Using the CLI 148

Invoking commands 148 ■ Creating and deploying functions 149

6.5 Lambda patterns 151

Async waterfall 152 ■ Series and parallel 157 ■ Using libraries 158 ■ Move logic to another file 161

6.6 Testing Lambda functions 161

Testing locally 161 ■ Writing tests 162 ■ Testing in AWS 164

6.7 Exercises 166 6.8 Summary 166

7.1 API Gateway as the interface 169

Integration with AWS services 170 ■ Caching, throttling, and logging 170 ■ Staging and versioning 171 ■ Scripting 171

7.2 Working with the API Gateway 171

The plan 173 ■ Creating the resource and method 174 Configuring method execution 177 ■ The Lambda function 180 ■ Updating the website 184

7.3 Optimizing the gateway 187

Throttling 187 ■ Logging 189 ■ Caching 191

7.4 Stages and versions 194

Creating a stage variable 195 ■ Using stage variables 195 Versions 196

7.5 Exercises 198 7.6 Summary 198

P ART 3 G ROWING YOUR A RCHITECTURE 199

8.1 Smarter storage 201

Versioning 202 ■ Hosting a static website 204 ■ Storage classes 206 ■ Object lifecycle management 207 ■ Transfer acceleration 209 ■ Event notifications 209

8.2 Secure upload 211

Architecture 212 ■ Upload policy Lambda 213 ■ S3 CORS configuration 218 ■ Uploading from the website 219

8.3 Restricting access to files 223

Removing public access 223 ■ Generating presigned URLs 224

8.4 Exercises 225

8.5 Summary 225

9.1 Introduction to Firebase 228

Data structure 228 ■ Security rules 230

9.2 Adding Firebase to 24-Hour Video 230

Architecture 231 ■ Setting up Firebase 233 ■ Modifying Transcode Video Lambda 234 ■ Transcode Video Firebase Update 239 ■ Connecting Lambda 241 ■ Website 242 End-to-end testing 248

9.3 Securing access to files 248

Signed URL Lambda 249 ■ API Gateway settings 250 Updating the website again 251 ■ Improving

performance 251 ■ Improving Firebase security 254

9.4 Exercises 259

9.5 Summary 259

10 Going the last mile 260

10.1 Deployment and frameworks 260

10.2 Toward better microservices 261

Handling errors 264

10.3 Step Functions 266

Image-processing example 267

10.4 AWS Marketplace 272

10.5 Where from here 274

appendix A Services for your serverless architecture 277

appendix B Installation and setup 282

appendix C More about authentication and authorization 293

appendix D Lambda insider 299

appendix E Models and mapping 305

appendix F S3 event message structure 321 appendix G Serverless Framework and SAM 323

foreword

BY PATRICK DEBOIS, DEVOPS JEDI

FOUNDER OF DEVOPSDAYSCTO, SMALL TOWN HEROESWrite programs that do one thing and do it well Write programs designed to worktogether These are the core ideas of the Unix philosophy, first articulated by Unixdesigner Ken Thompson In recent years, companies like Google, Netflix, Uber, andAirbnb have proven that in modern distributed systems you can easily replace theword programs with the word services The latest twist on this idea, serverless comput-ing, is a manifestation of how the intelligent combination of hosted services and self-managing infrastructure can result in significant improvements in development timeand operating cost

Serverless Architectures on AWS balances emerging serverless design patterns with a set

of practical, down-to-earth case studies, making it ideal for both beginners andadvanced practitioners Serverless is a new discipline, and this author succeeds in cov-ering a wide spectrum of topics without losing depth and focus He writes with clearpassion, an eye for detail, and a treasure trove of knowledge to share

Serverless computing requires a shift in how you build software architectures, and

as with many paradigm shifts, you have to unlearn some of your habits While beingenthusiastic about the new technology, the author goes to great lengths to point outthe benefits and limits of these new types of architectures As a bonus, he gives insightinto his own journey running a real-life serverless-based architecture His “put yourmoney where your mouth is” attitude shows the ultimate payoff of serverless, helpingyour business to focus and succeed

foreword

BY DR DONALD F FERGUSONCTO AND COFOUNDER, SEEKA TV

ADJUNCT PROFESSOR,

DEPARTMENT OF COMPUTER SCIENCE,

COLUMBIA UNIVERSITYMany technologies have profoundly transformed application development, testing,

and delivery Cloud computing and various forms of “as-a-service” are examples of

technologies that are redefining application development and delivery Many teamsand projects struggle and sometimes fail when attempting to exploit new technology.The primary reason for failure is applying the current application architecture andprogramming model to a radically different technology Well-designed, -imple-mented, and -delivered cloud-spanning applications are radically different from tradi-

tional applications Serverless Architectures on AWS does an excellent job of explainingthe new application architecture and provides detailed, practical guidance on how tosucceed

Infrastructure as a Service (IaaS), Software as a Service (SaaS) and Platform as aService (PaaS) are cloud versions of the on-premise application and infrastructurearchitecture The models deliver value but can never fully exploit the potential of thecloud SaaS provides semi-standard solutions to business problems but doesn’t enablerapid development and deployment of more targeted applications IaaS and PaaSdeliver resource usage efficiency but don’t eliminate the cost to configure and man-age software server infrastructure None of these models enable exploitation of the

explosion in web-callable APIs that form the API economy Serverless architectures are the

only architectures that eliminate the cost of server software and deliver the flexibility

to rapidly develop, deploy, and manage targeted, focused cloud applications

Part I—First Steps of this book provides the foundation for building serverless

archi-tecture The section explains the new architecture’s essential features and benefits.This includes a clear explanation of the technology’s pros and cons and guidance for

selection Equally important, the section introduces architecture design patterns Realizing

best practices through applying design patterns is the single most important factor inthe successful adoption of transformational computing technology The sectionexplains the patterns within the context of a real solution that the author implementedusing serverless architectures: “Code rules and slides drool.” The author’s practicalexperience and success are a primary reason for my recommending this book People often mistakenly equate serverless with a specific technology; for example,AWS Lambda functions Serverless architecture is much broader and includes UIdesign, publish/subscribe infrastructure, workflows/orchestration, active databases,API gateways and management, and data services In aggregate, these technologies

can be overwhelming Serverless Architectures on AWS explains the contributing ogies’ roles and uses The book also provides a detailed walkthrough on how to useAmazon Web Services’ implementation of the technology through building a workingapplication The initial cookbook and tutorial are core to being able to repeatably andreliably use the technology

The data layer and security are two of the hardest architecture areas of any

applica-tion Serverless Architectures on AWS has detailed sections on both topics The materialexplains the concepts (for example, authentication and authorization), positions theconcepts within application scenarios (for example, web applications), and providesconcrete, detailed examples of how to design and implement security and the datalayer The details include examples using non-AWS technology like Auth0 and GoogleFirebase

My company is building its solution using AWS and serverless architecture In thisendeavor I’ve found this book and the author’s other material to be essential to ourprogress I teach advanced topics in computer science at Columbia University, wherethe classes focus on internet applications and cloud-spanning applications Thisbook’s material is a foundation for much of what I teach My experience demonstrates

that Serverless Architectures on AWS is a pivotal book that’s crucial to exploitation ofcloud computing The detailed information about AWS within the context of a realapplication is priceless, and the concepts and patterns apply to any serverless solutionusing any technology

preface

The first time I heard about AWS Lambda was from Sam Kroonenburg Lambda hadjust been released, but Sam was already excited by its prospects He told me about exe-cution of functions in the cloud, the potential for automation within AWS, and devel-opment of event-driven workflows It was fascinating and full of endless potential Thethought of being able to run my code without having to provision or look after infra-structure seemed very cool and not a moment too soon As a software engineer, Ialways wanted to focus on architecture and code rather than infrastructure, opera-tions, and system management Here was my opportunity to do so with Amazon WebServices

After some months, the API Gateway came out and solved one of the biggest lems with Lambda at the time It became possible to invoke Lambda functions usingstandard HTTP requests The dream of creating fast, scalable back ends for applica-tions without having to touch a server was happening right in front of us The firstmajor serverless project I worked on, started by Sam Kroonenburg, was A Cloud Guru,which grew into a large learning-management system This platform, entirely server-less, cost very little to run and allowed for quick iteration cycles It was a lot of fun towork on because we could focus on adding business value and new features withouthaving to worry about infrastructure management or complex operations, and theplatform could scale like crazy

While building A Cloud Guru, we also realized that being serverless wasn’t justabout running code in Lambda It was also about using third-party services and prod-ucts We used a managed authentication service and a managed database that saved usweeks, if not months, of development time We identified aspects of our system thatwere important but that we didn’t need to build, like payment processing and cus-

tomer messaging We found great third-party services that worked brilliantly with ourserverless back end and integrated them with the rest of our system

The third key component was, of course, selecting the right patterns and tures We recognized that event-driven architectures were natural to serverless applica-tions, and we worked to make our entire system event-driven We thought aboutsecurity, reliability, and scalability, and how functions and back end services needed to

architec-be composed to make the most of them

Having helped to build one of the first large-scale serverless applications and ing reviewed other serverless systems since then, one thing is clear to me: the combi-nation of scalable cloud functions, reliable third-party services, and serverlessarchitectures and patterns is the next step in the evolution of cloud computing Overthe next few years, we’ll see startups and established enterprises adopt the serverlessapproach It will help them innovate and move more quickly than their competition.This book is a glimpse of what this future holds and an instruction manual for how to

hav-get started today I hope that you enjoy Serverless Architectures on AWS and join me onthis serverless journey

to none

Austen Collins, the creator of the Serverless Framework, made a major tion to the book in the form of a section on the Serverless Framework There’s no onebetter to write about a framework than its creator, so I’m thankful to Austen for volun-teering his time and effort I hope that everyone who reads this book—and, in partic-ular, reads Austen’s excellent treatise—spends time learning, understanding, andadopting the Serverless Framework

I’d also like to thank Sam Kroonenburg, who introduced me to the serverless wayand helped with thoughtful feedback and review throughout the writing of this book.Sam’s enthusiasm for AWS Lambda and ideas on architecture and design inspired me

to put pen to paper in the first place Another special thank-you goes to Ryan Brown,who read the book and gave detailed, blow-by-blow commentary and critique Thisbook is far better for Ryan’s reading and careful and considered feedback

Additional thanks must go out to Donald Ferguson and Patrick Debois for writingtwo very special forewords Donald and Patrick have done a lot for software engineer-ing and for the serverless community especially I’m in awe of their accomplishmentsand very thankful for their time and involvement

I’d like to thank a few others who gave me feedback and encouragement Thesepeople include Ryan Kroonenburg, Mike Chambers, John McKim, Adrian Cantrill,Daniel Parker, Allan Brown, Nick Triantafillou, Drew Firment, Neil Walker, AlexMackey, and Ilia Mogilevsky I’d like to thank Mike Stephens of Manning, Kostas Passa-dis, and David Fombella Pombal for helping to bring this book to fruition In addi-tion, these acknowledgments wouldn’t be complete if I didn’t thank the Manningreviewers who generously read and commented on the text during its development,including Alain Couniot, Andy Wiesendanger, Colin Joyce, Craig Smith, DanielVásquez, Diego Santiviago, John Huffman, Josiah Dykstra, Kent R Spillner, MarkusBreuer, Saioa Picado Fernández, Sau Fai Fong, Sean Hull, and Vijaykumar Borkar Finally, I’d like to thank my family, including my dad and brother, and all my otherrelatives, for finding the inner strength to listen to me talk about the book at everygathering And I’d like to thank Durdana Masud, who helped me greatly throughout

my writing, starting with positive cheer and inspiration to looking at umpteen colorpalettes in an effort to help me select colors for the original images used in the manu-script Thank you

about this book

Whether you are a beginner or an expert, just starting out in IT or have years of rience, this book will take you on a journey through serverless architectures You’lllearn about key patterns, find out about the pros and cons of applying serverlessmethodologies, and build your own serverless video-sharing website using AWSLambda, API Gateway, Elastic Transcoder, S3, Auth0, and Firebase You’ll also learn alot about AWS and recommended frameworks for organizing and deploying yourserverless applications

This book is organized into three parts The first takes you through basic serverlessprinciples and discusses key architectures and patterns You begin building your firstevent-driven pipeline using AWS Lambda and learn about key AWS services, like theomnipresent and all-powerful Identity and Access Management service

The second part focuses on authentication and authorization, AWS Lambda, andthe API Gateway All chapters in this part are important to understanding and buildingserverless applications After you read and work through them, you’ll have a thoroughgrasp of the key technologies needed for serverless applications

The third part addresses those additional services and architectures needed tobuild real-world applications A key focus is file and data storage using S3 and Google’sFirebase, respectively The final chapter adds more information about some of thetechniques and services that you can apply to grow your serverless applications

At the end of the book, you’ll find seven appendixes that give you additional mation on various topics The last appendix, for example, covers the Serverless Frame-work and the Serverless Application Mode (SAM); you should definitely read throughand try the steps in this appendix

infor-AWS and other services like Auth0 and Firebase evolve quickly, so don’t be prised if some of the screenshots or instructions are different by the time you read thisbook The fundamentals of serverless event-driven architectures remain the same, butsome of the minor things, such as button positioning or labels, may change over time.This book is suitable for developers and solution architects who are new to AWS andcloud computing, as well as for those who are veterans My hope is that you’ll discover

sur-a new wsur-ay to build sur-applicsur-ations thsur-at is chesur-aper, more scsur-alsur-able, sur-and hesur-aps more fun!

Code conventions

This book provides many examples of code These appear throughout the text and asseparate code listings Code appears in a fixed-width font just like this, so you’llknow when you see it

Getting the source code

All of the source code used in the book is available on the Manning website(https://manning.com/books/serverless-architectures-on-aws) or in my GitHubrepository (https://github.com/sbarski/serverless-architectures-aws) I love GitHub,

so if you’d like to contribute to the source code, please open a pull request If you see

a problem, please file an issue

Author online

Purchase of Serverless Architectures on AWS includes free access to a private web forumrun by Manning Publications where you can make comments about the book, asktechnical questions, and receive help from the lead author and from other users Toaccess the forum and subscribe to it, point your web browser to www.manning.com/books/serverless-architectures-on-aws This page provides information on how to get

on the forum once you are registered, what kind of help is available, and the rules ofconduct on the forum

Manning’s commitment to our readers is to provide a venue where a meaningfuldialog between individual readers and between readers and the author can take place

It is not a commitment to any specific amount of participation on the part of theauthor, whose contribution to the forum remains voluntary (and unpaid) We suggestyou try asking the author some challenging questions lest his interest stray! TheAuthor Online forum and the archives of previous discussions will be accessible fromthe publisher’s website as long as the book is in print

about the author

PETER SBARSKI is Vice President of Engineering at A Cloud Guruand the organizer of Serverlessconf, the world’s first conferencededicated entirely to serverless architectures and technologies

He enjoys running in-person workshops and writing an sional blog post on serverless architectures Peter has an exten-sive career working in IT and has led teams across largeenterprise solutions with a focus on web and AWS cloud technologies His specialtiesinclude back end architecture, microservices, and orchestration of systems

Peter holds a PhD in computer science from Monash University, Australia, and can

be followed on Twitter (@sbarski) and GitHub (https://github.com/sbarski)

about the coverThe figure on the cover of Serverless Architectures on AWS is captioned “Man fromStupno/Sisak, Croatia.” The illustration is taken from a reproduction of an album ofCroatian traditional costumes from the mid-nineteenth century by Nikola Arsenovic´,published by the Ethnographic Museum in Split, Croatia, in 2003 The illustrationswere obtained from a helpful librarian at the Ethnographic Museum in Split, itself sit-uated in the Roman core of the medieval center of the town: the ruins of EmperorDiocletian’s retirement palace from around AD304 The book includes finely coloredillustrations of figures from different regions of Croatia, accompanied by descriptions

of the costumes and of everyday life

Dress codes and lifestyles have changed over the last 200 years, and the diversity byregion, so rich at the time, has faded away It’s now hard to tell apart the inhabitants ofdifferent continents, let alone of different hamlets or towns separated by only a fewmiles Perhaps we have traded cultural diversity for a more varied personal life—cer-tainly for a more varied and fast-paced technological life Manning celebrates theinventiveness and initiative of the computer business with book covers based on therich diversity of regional life of two centuries ago, brought back to life by illustrationsfrom old books and collections like this one

Part 1 First steps

You’re now taking the first steps toward mastery of serverless architectures.The first part of this book takes you through the concepts and introduces you tothe five principles of serverless architectures You’ll learn about several usefuldesigns and architectures, and you’ll begin building your own media-transcodingpipeline using Lambda, S3, and the Elastic Transcoder Beginning with the thirdchapter and continuing thereafter, you’ll find fun exercises to try in your sparetime These exercises are optional but highly recommended, because they’llreinforce your knowledge and understanding of serverless technologies andarchitectures

Going serverless

If you ask software developers what software architecture is, you might get answersranging from “it’s a blueprint or a plan” to “a conceptual model” to “the big pic-ture.” It’s undoubtedly true that architecture, or lack thereof, can make or breaksoftware Good architecture may help to scale a web or mobile application, andpoor architecture may cause serious issues that necessitate a costly rewrite Under-standing the implication of choice regarding architecture and being able to planahead is paramount to creating effective, high-performing, and ultimately success-ful software systems

This book is about how to go beyond traditional back-end architectures thatrequire you to interact with a server in some shape or form It describes how to create

This chapter covers

 Traditional system and application architectures

 Key characteristics of serverless architectures

and their benefits

 How serverless architectures and microservices

fit into the picture

 Considerations when transitioning from server to

serverless

serverless back ends that rely entirely on a compute service such as Amazon Web Services

(AWS) Lambda and an assortment of useful third-party APIs, services, and products Itshows how to build the next generation of systems that can scale and handle demand-ing computational requirements without having to provision or manage a single server.Importantly, this book describes techniques that can help developers quickly deliverproducts to market while maintaining a high level of quality and performance by usingservices and architectures that today’s cloud has to offer

The first chapter of this book is about why we think serverless is a game changerfor software developers and solution architects This chapter introduces key servicessuch as AWS Lambda and describes the principles of serverless architecture to helpyou understand what makes a true serverless system

1.1 How we got to where we are

If you look at systems powering most of today’s web-enabled software, you’ll see end servers performing various forms of computation and client-side front ends pro-viding an interface for users to operate via their browser, mobile, or desktop device

In a typical web application, the server accepts HTTP requests from the front endand processes requests Data might travel through numerous application layersbefore being saved to a database The back end, finally, generates a response—itcould be in the form of JSON or fully rendered markup—which is sent back to the cli-ent (figure 1.1) Naturally, most systems are more complex once elements such asload balancing, transactions, clustering, caching, messaging, and data redundancyare taken into account Most of this software requires servers running in data centers

or in the cloud that need to be managed, maintained, patched, and backed up Provisioning, managing, and patching of servers is a time-consuming task thatoften requires dedicated operations people A non-trivial environment is hard to set

up and operate effectively Infrastructure and hardware are necessary components ofany IT system, but they’re often also a distraction from what should be the corefocus—solving the business problem

Over the past few years, technologies such as platform as a service (PaaS) and ers have appeared as potential solutions to the headache of inconsistent infrastructure

contain-What’s in a name?

Before we start, we should mention that the word serverless is a bit of a misnomer.

Whether you use a compute service such as AWS Lambda to execute your code, orinteract with an API, there are still servers running in the background The difference

is that these servers are hidden from you There’s no infrastructure for you to thinkabout and no way to tweak the underlying operating system Someone else takescare of the nitty-gritty details of infrastructure management, freeing your time forother things Serverless is about running code in a compute service and interactingwith services and APIs to get the job done

environments, conflicts, and server management overheard PaaS is a form of cloudcomputing that provides a platform for users to run their software while hiding some

of the underlying infrastructure To make effective use of PaaS, developers need towrite software that targets the features and capabilities of the platform Moving a legacyapplication designed to run on a standalone server to a PaaS service often leads toadditional development effort because of the ephemeral nature of most PaaS imple-mentations Still, given a choice, many developers would understandably choose to usePaaS rather than more traditional, more manual solutions thanks to reduced mainte-nance and platform support requirements

Containerization is a way of isolating an application with its own environment It’s

a lightweight alternative to full-blown virtualization Containers are isolated and weight but they need to be deployed to a server—whether in a public or private cloud

light-or onsite They’re an excellent solution when dependencies are in play, but they havetheir own housekeeping challenges and complexities They’re not as easy as beingable to run code directly in the cloud

Finally, we make our way to Lambda, which is a compute service from Amazon WebServices Lambda can execute code in a massively parallelized way in response toevents Lambda takes your code and runs it without any need to provision servers,install software, deploy containers, or worry about low-level detail AWS takes care ofprovisioning and management of their Elastic Compute Cloud (EC2) servers that runthe actual code and provides a high-availability compute infrastructure—includingcapacity provisioning and automated scaling—that the developer doesn’t need to

think about The words serverless architectures refer to these new kinds of software

archi-tectures that don’t rely on direct access to a server to work By taking Lambda andmaking use of various powerful single-purpose APIs and web services, developers can

build loosely coupled, scalable, and efficient architectures quickly Moving away from

servers and infrastructure concerns, as well as allowing the developer to primarily focus on code,

is the ultimate goal behind serverless.

1 User performs an action

that requires data from a

database to be displayed.

2 A request is formed and sent from the client

to the web server.

3 The request is processed and the database is queried.

Database (data tier)

Figure 1.1 This is a basic request-response (client-server) message exchange pattern that most developers are familiar with There’s only one web server and one database in this figure Most systems are much more complex.

1.1.1 Service-oriented architecture and microservices

Among system and application architectures, service-oriented architecture (SOA) has

a lot of name recognition among software developers It’s an architecture that clearlyconceptualized the idea that a system can be composed of many independent services.Much has been written about SOA, but it remains controversial and misunderstoodbecause developers often confuse design philosophy with specific implementationand attributes

SOA doesn’t dictate the use of any particular technology Instead, it encourages anarchitectural approach in which developers create autonomous services that commu-nicate via message passing and often have a schema or a contract that defines howmessages are created or exchanged Service reusability and autonomy, composability,granularity, and discoverability are all important principles associated with SOA Microservices and serverless architectures are spiritual descendants of service-oriented architecture They retain many of the aforementioned principles andideas while attempting to address the complexity of old-fashioned service-orientedarchitectures

ON MICROSERVICES

There has been a recent trend to implement systems with microservices Developerstend to think of microservices as small, standalone, fully independent services builtaround a particular business purpose or capability

Ideally, microservices should be easy to replace, with each service written in anappropriate framework and language The mere fact that microservices can be written

in different general-purpose or domain-specific languages (DSL) is a drawing card formany developers Benefits can be gained from using the right language or a special-ized set of libraries for the job Nevertheless, it can often be a trap, too Having a mix

of languages and frameworks can be hard to support, and, without strict discipline,can lead to confusion down the road

Each microservice can maintain state and store data And if microservices are rectly decoupled, development teams can work and deploy microservices inde-pendently of one another On the other hand, eventual consistency, transactionmanagement, and complex error recovery can make things more difficult (especiallywithout a sound plan)

It can be argued that serverless architecture embodies many principles frommicroservices too After all, depending on how you design the system, every computefunction could be considered to be its own standalone service But you don’t need tofully embrace the microservices mantra if you don’t want to

Serverless architectures give you the freedom to apply as few or as many microserviceprinciples as you would like without forcing you down a single path This book showsexamples of architectures where parts of a monolithic system are re-implemented asserverless architecture without applying all of the microservices tenets It’s then up toyou to decide how far to take your architecture based on your requirements and prefer-ence (chapter 10 has more to say on the issue of microservices and design)

1.1.2 Software design

Software design has evolved from the days of code running on a mainframe to tier systems where the presentation, data, and application/logic tiers feature promi-nently in many designs Within each tier there may be multiple logical layers that dealwith particular aspects of functionality or domain There are also cross-cutting compo-nents, such as logging or exception-handling systems, that can span numerous layers.The preference for layering is understandable Layering allows developers to decou-ple concerns and have more maintainable applications

But the converse can also be true Having too many layers can lead to inefficiencies

A small change can often cascade and cause the developer to modify every layer out the system, costing considerable time and energy in implementation and testing.The more layers there are, the more complex and unwieldy the system might becomeover time Figure 1.2 shows an example of a tiered architecture with multiple layers Serverless architectures can help with the problem of layering and having toupdate too many things There’s room for developers to remove or minimize layering

through-by breaking the system into functions and allowing the front end to securely nicate with services and even the database directly, as shown in figure 1.3 All of thiscan be done in an organized way to prevent spaghetti implementations and depen-dency nightmares by clearly defining service boundaries, allowing Lambda functions

commu-to be aucommu-tonomous, and planning how functions and services will interact

Application user

User interface components Layering helps to

segregate concerns, but more layers can also make changes harder and slower to implement.

Cross-cutting concerns span numerous layers

A good example of this is logging, which can happen

at every layer.

Application tier

Cross-cutting concerns

Presentation

tier

Data tier

Presentation logic Client-side model Client-side service layer

Application programming interface Server-side service layer Business/domain layer Business entities/model Data access/persistence layer

Database File storage

Figure 1.2 A typical three-tier application is usually made up of presentation, application, and data

A serverless approach doesn’t solve all problems, nor does it remove the underlyingintricacies of the system But when implemented correctly it can provide opportuni-ties to reduce, organize, and manage complexity A well-planned serverless architec-ture can make future changes easier, which is an important factor for any long-termapplication The next section and later chapters discuss the organization and orches-tration of services in more detail

Application user

Lambda functions can

communicate with other

AWS products and make

calls to non-AWS services.

Presentation tier

Payment service

API gateway

Lambda function

Notification service

Lambda function

Log service

File storage

Lambda function

Analytics service

Authentication

Figure 1.3 In a serverless architecture there’s no single traditional back end The front end

of the application communicates directly with services, the database, or compute functions

via an API gateway Some services, however, must be hidden behind compute service

functions, where additional security measures and validation can take place.

Tiers vs layers

There is confusion among some developers about the difference between layers and

tiers A tier is a module boundary that exists to provide isolation between major

com-ponents of a system A presentation tier that’s visible to the user is separate fromthe application tier, which encompasses business logic In turn, the data tier isanother separate system that can manage, persist, and provide access to data Com-ponents grouped in a tier can physically reside on different infrastructures

1.2 Principles of serverless architectures

Here we define five principles of serverless architectures that describe how an idealserverless system should be built Use these principles to help guide your decisionswhen building serverless applications:

1 Use a compute service to execute code on demand (no servers)

2 Write single-purpose stateless functions

3 Design push-based, event-driven pipelines

4 Create thicker, more powerful front ends

5 Embrace third-party services

Let’s look at each of these principles in more detail

1.2.1 Use a compute service to execute code on demand

Serverless architectures are a natural extension of ideas raised in SOA In serverlessarchitecture all custom code is written and executed as isolated, independent, andoften granular functions that are run in a stateless compute service such as AWSLambda Developers can write functions to carry out almost any common task, such

as reading and writing to a data source, calling out to other functions, and ing a calculation In more complex cases, developers can set up more elaborate pipe-lines and orchestrate invocations of multiple functions There might be scenarioswhere a server is still needed to do something These cases, however, may be far andfew between, and as a developer you should avoid running and interacting with aserver if possible

perform-Layers are logical slices that carry out specific responsibilities in an application Each

tier can have multiple layers within it that are responsible for different elements offunctionality such as domain services

So, what is Lambda exactly?

AWS Lambda is a compute service that executes code written in JavaScript (node.js),Python, C#, or Java on AWS infrastructure Source code (JARs or DLLs in case of Java

or C#) is zipped up and deployed to an isolated container that has an allocation ofmemory, disk space, and CPU The combination of code, configuration, and depen-

dencies is typically referred to as a Lambda function The Lambda runtime can invoke

a function multiple times in parallel Lambda supports push and pull event models ofoperation and integrates with a large number of AWS services Chapter 6 coversLambda in more detail, including its event model, methods of invocation, and bestpractice with regard to design Note that Lambda isn’t the only game in town Micro-soft Azure Functions, IBM Bluemix, OpenWhisk, and Google Cloud Functions are othercompute services you might want to look at

1.2.2 Write single-purpose stateless functions

As a software engineer, you should try to design your functions with the single sibility principle (SRP) in mind A function that does just one thing is more testableand robust and leads to fewer bugs and unexpected side effects By composing andcombining functions and services in a loose orchestration, you can build complexback-end systems that are still understandable and easy to manage A granular func-tion with a well-defined interface is also more likely to be reused within a serverlessarchitecture

Code written for a compute service such as Lambda should be created in a stateless

style It must not assume that local resources or processes will survive beyond theimmediate session (chapter 6 has more to say on this) Statelessness is powerfulbecause it allows the platform to quickly scale to handle an ever-changing number ofincoming events or requests

1.2.3 Design push-based, event-driven pipelines

Serverless architectures can be built to serve any purpose Systems can be built less from scratch, or existing monolithic applications can be gradually reengineered

server-to take advantage of this architecture The most flexible and powerful serverlessdesigns are event-driven In chapter 3, for example, you’ll build an event-driven, push-based pipeline to see how quickly you can put together a system to encode video todifferent bitrates and formats You’ll achieve this by connecting Amazon’s SimpleStorage Service (S3), Lambda, and Elastic Transcoder together (figure 1.4)

Building event-driven, push-based systems will often reduce cost and complexity(you won’t need to run extra code to poll for changes) and potentially make the over-all user experience smoother It goes without saying that although event-driven, push-based models are a good goal, they might not be appropriate or achievable in all cir-cumstances Sometimes you’ll have to implement a Lambda function that polls theevent source or runs on a schedule We’ll cover different event models and you’ll workthrough examples in later chapters

1.2.4 Create thicker, more powerful front ends

It’s important to remember that custom code running in Lambda should be quick toexecute Functions that terminate sooner are cheaper because Lambda pricing isbased on the number of requests, the duration of execution, and the amount of allo-cated memory Having less to do in Lambda is cheaper Moreover, building a richfront end (in lieu of a complex back end) that can talk to third-party services directlycan be conducive to a better user experience Fewer hops between online resourcesand reduced latency will result in a better perception of performance and usability ofthe application In other words, you don’t have to route everything through a com-pute service Your front end may be able to communicate directly with a search pro-vider, a database, or another useful API

Digitally signed tokens can allow front ends to talk to disparate services, includingdatabases, in a secure manner This is in contrast to traditional systems where all com-munication flows through the back-end server.

Not everything, however, can or should be done in the front end There are secretsthat cannot be trusted to the client device Processing a credit card or sending emails

to subscribers must be done only by a service that runs outside the end user’s control

In this case, a compute service must be used to coordinate action, validate data, andenforce security

The other important point to consider is consistency If the front end is ble for writing to multiple services and fails midway through, it can leave the system in

responsi-an inconsistent state In this scenario, a Lambda function should be used because itcan be designed to gracefully handle errors and retry failed operations

Upload new

video file

Create transcode job

Transcode video

Save new videos

Update metadata

Dispatch

notification

Create notification

Save metadata to database

1 Simple Storage Service.

A Lambda function responds

to the event and creates an Elastic Transcoder job to create new videos from the source file.

3 Elastic Transcoder.

Transcoding service executes the job and encodes new videos.

4 Simple Storage Service.

The newly encoded videos are saved to a new S3 bucket by the Elastic Transcoder.

This triggers another event.

7 Lambda Function.

A change to the database automatically triggers a Lambda function that creates

1.2.5 Embrace third-party services

Third-party services are welcome to join the show if they can provide value and reducecustom code It goes without saying, however, that when a third-party service is consid-ered, factors such as price, capability, availability, documentation, and support must

be assessed It’s far more useful for developers to spend time solving a problemunique to their domain than re-creating functionality already implemented by some-one else Don’t build for the sake of building if viable third-party services and APIs areavailable Stand on the shoulders of giants to reach new heights Appendix A has ashort list of Amazon Web Services and non-Amazon Web Services we’ve found useful.We’ll look at most of those services in more detail as we move through the book

1.3 Transitioning from a server to services

One advantage of the serverless approach is that existing applications can be ally converted to serverless architecture If a developer is faced with a monolithic codebase, they can gradually tease it apart and create Lambda functions that the applica-tion can communicate with

The best approach is to initially create a prototype to test developer assumptionsabout how the system would function if it was going to be partly or fully serverless.Legacy systems tend to have interesting constraints that require creative solutions; and

as with any architectural refactors at a large scale, there are inevitably going to becompromises The system may end up being a hybrid—see figure 1.5—but it may bebetter to have some of its components use Lambda and third-party services ratherthan remain with an unchanged legacy architecture that no longer scales or thatrequires expensive infrastructure to run

The transition from a legacy, server-based application to a scalable serverless tecture may take time to get right It needs to be approached carefully and slowly, anddevelopers need to have a good test plan and a great DevOps strategy in place beforethey begin

archi-1.4 Serverless pros and cons

There are advantages to implementing a system as fully or partially serverless, ing reduced cost and accelerated time to market But you need to carefully considerthe road to serverless architecture in the context of the application being created

includ-1.4.1 Decision drivers

Serverless is not a silver bullet in all circumstances It may not be appropriate forlatency-sensitive applications or software with specific service-level agreements (SLA).Vendor lock-in can be an issue for enterprise and government clients, and decentral-ization of services can be a challenge

NOT FOR EVERYONE

Lambda runs in a public cloud, so mission-critical applications shouldn’t necessarily

be based on it A banking system that performs high-volume transactions or a patient

life-support system requires a higher level of performance and reliability than a publiccloud system can provide It’s possible that organizations could employ dedicatedhardware or run private or hybrid clouds with their own compute services that mightmeet serviceability and reliability requirements In that case, these architectures could

be adopted

SERVICE LEVELS

AWS has an SLA for some services but not for others, so that may be a factor in yourdecision For most systems, the reliability offered by AWS is sufficient, but some enter-prise use cases may require additional guarantees Non-AWS third-party services are inthe same boat Some may have strong SLAs, whereas others may not have one at all

CUSTOMIZATION

When it comes to Lambda, the efficiencies gained from having Amazon look after theplatform and scale functions come at the expense of being able to customize the oper-ating system or tweak the underlying instance You can modify the amount of RAMallocated to a function and change timeouts, but that’s about it (see chapter 6 formore information) Similarly, different third-party services will have varying levels ofcustomization and flexibility

Lambda function

Lambda function

Lambda function

Payment service

Notification service

Search service

A monolithic application

can be deconstructed

into Lambda functions,

third-party services, IaaS,

PaaS, and containers.

The combination of

technologies should depend

on your needs and constraints

However, more technologies

require more overhead, time,

and energy

Containers, PaaS, IaaS, Lambda functions, and services can talk to one another If you have designed a system using a combination of the above technologies you must consider how orchestration of events will take place

Figure 1.5 Serverless architecture is not an all-or-nothing proposition If you currently have

a monolithic application running on servers, you can begin to gradually extract components

and run them in isolated services or compute functions You can decouple a monolithic

application into an assortment of infrastructure as a service (IaaS), PaaS, containers,

Lambda functions, and third-party services if it helps.

Moving from a monolithic approach to a more decentralized serverless approachdoesn’t automatically reduce the complexity of the underlying system either The dis-tributed nature of the solution can introduce its own challenges because of the need

to make remote rather than in-process calls and the need to handle failures andlatency across a network

1.4.2 When to use serverless

Serverless architecture allows developers to focus on software design and code ratherthan infrastructure Scalability and high availability are easier to achieve, and the pric-ing is often fairer because you pay only for what you use Importantly with serverless,you have a potential to reduce some of the complexity of the system by minimizingthe number of layers and amount of code you need

NO MORE SERVERS

Tasks such as server configuration and management, patching, and maintenance aretaken care of by the vendor, which saves time and money Amazon looks after thehealth of its fleet of servers that power Lambda If you don’t have specific require-ments to manage or modify compute resources, then having Amazon or another ven-dor look after them is a great solution You’re responsible only for your own code,leaving operational and administrative tasks to a different set of capable hands

MANY USES

The statelessness and scalability of compute can be used to solve problems that fit from parallel processing Back ends for CRUD applications, e-commerce, back-office systems, complex web apps, and all kinds of mobile and desktop software can

bene-be built quickly using serverless architectures Tasks that used to take weeks can bene-bedone in days or hours as long as the right combination of technologies is chosen Aserverless approach can work exceptionally well for startups that want to innovateand move quickly

LOW COST

The traditional server-based architecture requires servers that don’t necessarily run atfull capacity all of the time Scaling, even with automated systems, involves a newserver, which is often wasted until there’s a temporary upsurge in traffic or new data.Serverless systems are much more granular with regard to scaling and are cost-effective, especially when peak loads are uneven or unexpected With Lambda youonly pay for what you use (chapter 4 shows how to calculate cost for Lambda and theAPI Gateway)

LESS CODE

We mentioned at the start of the chapter that serverless architecture provides anopportunity to reduce some of the complexity and code in comparison to more tradi-tional systems There’s less need to have a multilayered back-end system, especially ifyou allow the front end to do more work and talk to services (and the database)directly

SCALABLE AND FLEXIBLE

As a developer you don’t need to use serverless architecture to replace your entireback end if you don’t want to or are unable to do so You can use Lambda to solve spe-cific problems, especially if they stand to benefit from parallelization It goes withoutsaying that serverless systems can scale more easily than traditional systems For exam-ple, consider the following solutions:

 ConnectWise, an IT services company, uses Lambda to process inbound logs,which has reduced their server maintenance needs from weeks to hours(https://aws.amazon.com/solutions/case-studies/connectwise/)

 Netflix uses Lambda to automate validation of backup completions and mate the encoding process of media files (https://aws.amazon.com/solutions/case-studies/netflix-and-aws-lambda/)

auto-You can use Lambda for extract, transform, and load (ETL) jobs, real-time file ing, and virtually anything else without having to touch your existing codebase Justwrite a function and run it

The cloud has been and continues to be a game changer for IT infrastructure andsoftware development Software developers need to think about the ways they canmaximize use of cloud platforms to gain a competitive advantage

Serverless architectures are the latest advance for developers and organizations tothink about, study, and adopt This exciting new shift in architecture will grow quickly

as software developers embrace compute services such as AWS Lambda And, in manycases, serverless applications will be cheaper to run and faster to implement

There’s also a need to reduce complexity and costs associated with running structure and carrying out development of traditional software systems The reduction

infra-in cost and time spent on infra-infrastructure mainfra-intenance and the benefits of scalability aregood reasons for organizations and developers to consider serverless architectures

In this chapter you learned what serverless architecture is, looked at its principles,and saw how it compares to traditional architectures In the next chapter, we’llexplore important architectures and patterns, and we’ll discuss specific use caseswhere serverless architectures were used to solve a problem

Architectures and patterns

What are the use cases for serverless architectures, and what kinds of architecturesand patterns are useful? We’re often asked about use cases as people learn about aserverless approach to the design of systems We find that it’s helpful to look at howothers have applied technology and what kinds of use cases, designs, and architec-tures they’ve produced Our discussion will center on these use cases and samplearchitectures This chapter will give you a solid understanding of where serverlessarchitectures are a good fit and how to think about design of serverless systems

This chapter covers

 Use cases for serverless architectures

 Examples of patterns and architectures

2.1.1 Application back end

In this book you’re going to build a back end for a media-sharing, YouTube-like cation It will allow users to upload video files, transcode these files to different play-able formats, and then allow other users to view them You’ll construct an entirelyserverless back end for a fully featured web application with a database and a RESTfulAPI And we’re going to show that serverless technologies are appropriate for buildingscalable back ends for all kinds of web, mobile, and desktop applications

Technologies such as AWS Lambda are relatively new, but we’ve already seen largeserverless back ends that power entire businesses Our serverless platform, called ACloud Guru (http://acloud.guru), supports many thousands of users collaborating inreal time and streaming hundreds of gigabytes of video Another example is Instant(http://instant.cm), which is a serverless content management system for static web-sites And yet another example is a hybrid-serverless system built by EPX Labs We’lldiscuss all of these systems later in the chapter

Apart from web and mobile applications, serverless is a great fit for IoT tions Amazon Web Services (AWS) has an IoT platform (https://aws.amazon.com/iot-platform/how-it-works/) that combines the following:

applica- Authentication and authorization

 Communications gateway

 Registry (a way to assign a unique identity to each device)

 Device shadowing (persistent device state)

 A rules engine (a service to transform and route device messages to AWS services)The rules engine, for example, can save files to Amazon’s Simple Storage Service (S3),push data to an Amazon Simple Queue Service (SQS) queue, and invoke AWS Lambdafunctions Amazon’s IoT platform makes it easy to build scalable IoT back ends fordevices without having to run a server

A serverless application back end is appealing because it removes a lot of structure management, has granular and predictable billing (especially when a server-less compute service such as Lambda is used), and can scale well to meet unevendemand

infra-2.1.2 Data processing and manipulation

A common use for serverless technologies is data processing, conversion, tion, and transcoding We’ve seen Lambda functions built by other developers for pro-cessing of CSV, JSON, and XML files; collation and aggregation of data; image resizing;and format conversion Lambda and AWS services are well suited for building event-driven pipelines for data-processing tasks

In chapter 3, you’ll build the first part of your application, which is a powerful line for converting videos from one format to another This pipeline will set file per-missions and generate metadata files It will run only when a new video file is added to

pipe-a designpipe-ated S3 bucket, mepipe-aning thpipe-at you’ll ppipe-ay only for execution of Lpipe-ambdpipe-a when