Slide 1

Slide 1 text

© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Danilo Poccia, Technical Evangelist [email protected] Serverless by Example: Building A Real-Time Chat System @danilop danilop

Slide 2

Slide 2 text

“Where” is Serverless?

Slide 3

Slide 3 text

Client Back End AWS Lambda

Slide 4

Slide 4 text

CDN Client Back End Devices Sensors Actuators AWS Lambda Gateway

Slide 5

Slide 5 text

AWS Greengrass

Slide 6

Slide 6 text

Lambda Functions on a Raspberry Pi AWS Greengrass Lambda Function

Slide 7

Slide 7 text

AWS Snowball Edge 100TB + Greengrass Core (≃ EC2 m4.4xlarge instance)

Slide 8

Slide 8 text

Snowball Edge Use Cases “Snowball Edge enables us to extend the innovative capabilities of HealthSuite, our cloud- enabled connected health ecosystem of devices, applications and digital tools supported by AWS, even when there is no network support.” Embedded Applications —Dale Wiggins, Business Leader, HealthSuite digital platform, Philips

Slide 9

Slide 9 text

Snowball Edge Use Cases “With AWS Snowball Edge, we can now collect 100 TB of data with no intermediate steps, and we can also analyze the images immediately using the onboard compute capabilities.” Remote Locations for data collection and analysis — Bob Cowen, Director of Hatfield Marine Research Center, Oregon State University

Slide 10

Slide 10 text

AWS Lambda@Edge Customize content delivery while reducing load on the origin Events / Triggers Take serverless to your users

Slide 11

Slide 11 text

Lambda@Edge Use Cases Demo build of a CloudFront+S3 distribution, using Lambda@Edge to secure its HTTP headers

Slide 12

Slide 12 text

Lambda@Edge Use Cases These processes include applying transactional labels to purchases so Blockbuster can track customer activity, and providing personalized recommendations based on previous purchases. Blockbuster runs serverless compute processes across AWS Regions and Amazon CloudFront edge locations (using Lambda@Edge) without provisioning or managing servers.

Slide 13

Slide 13 text

Let’s build a Web Chat…

Slide 14

Slide 14 text

Web Browser

Slide 15

Slide 15 text

Web Browser CloudFront Edge Location S3 Bucket HTTPS Static Content (HTML, CSS, JS)

Slide 16

Slide 16 text

Web Browser CloudFront Edge Location S3 Bucket HTTPS Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS)

Slide 17

Slide 17 text

Web Browser CloudFront Edge Location S3 Bucket Amazon API Gateway Lambda Function(s) DynamoDB Table(s) HTTPS Dynamic Content Database Access Execute Functions Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS)

Slide 18

Slide 18 text

Let’s make it more interactive…

Slide 19

Slide 19 text

Web Browser CloudFront Edge Location S3 Bucket Amazon API Gateway Lambda Function(s) DynamoDB Table(s) AWS IoT Topic(s) HTTPS Dynamic Content Database Access MQTT over Secure WebSockets (Publish, Subscribe) Execute Functions Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS)

Slide 20

Slide 20 text

Web Browser CloudFront Edge Location S3 Bucket Amazon API Gateway Lambda Function(s) DynamoDB Table(s) AWS IoT Topic(s) AWS IoT Rule(s) HTTPS Dynamic Content Database Access MQTT over Secure WebSockets (Publish, Subscribe) Subscribe Republish Execute Functions Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS)

Slide 21

Slide 21 text

Web Browser CloudFront Edge Location S3 Bucket Amazon API Gateway Lambda Function(s) DynamoDB Table(s) AWS IoT Topic(s) AWS IoT Rule(s) HTTPS Dynamic Content Database Access MQTT over Secure WebSockets (Publish, Subscribe) Subscribe Republish Execute Functions Execute Functions Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS) Publish

Slide 22

Slide 22 text

Web Browser CloudFront Edge Location S3 Bucket Amazon API Gateway Lambda Function(s) DynamoDB Table(s) AWS IoT Topic(s) AWS IoT Rule(s) HTTPS Dynamic Content Database Access MQTT over Secure WebSockets (Publish, Subscribe) Subscribe Republish Execute Functions Write to DynamoDB Execute Functions Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS) Publish

Slide 23

Slide 23 text

Web Browser CloudFront Edge Location S3 Bucket Amazon API Gateway Lambda Function(s) DynamoDB Table(s) AWS IoT Topic(s) AWS IoT Rule(s) Kinesis Stream(s) HTTPS Dynamic Content Database Access MQTT over Secure WebSockets (Publish, Subscribe) Subscribe Republish Execute Functions Streaming Data Write to DynamoDB Execute Functions Execute Functions (Micro-Batches) Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS) Publish

Slide 24

Slide 24 text

Web Browser CloudFront Edge Location S3 Bucket Amazon API Gateway Lambda Function(s) DynamoDB Table(s) AWS IoT Topic(s) AWS IoT Rule(s) Kinesis Stream(s) HTTPS Dynamic Content Database Access MQTT over Secure WebSockets (Publish, Subscribe) Subscribe Republish Execute Functions Streaming Data Write to DynamoDB Execute Functions Execute Functions (Micro-Batches) Amazon Cognito Authentication (AWS Temporary Credentials) Static Content (HTML, CSS, JS) Publish

Slide 25

Slide 25 text

What about Topics & Rules?

Slide 26

Slide 26 text

Web Browser AWS IoT Topics chat/in/${iot:ClientId} chat/out chat/pub/${room} chat/stream $aws/events/# Each client has a secure “input” topic to receive content from the back end All client can publish on an “output” topic, they are recognizable by their clientId All client can subscribe and receive from “public” topics Another “output” topic optimized for high volumes AWS IoT Lifecycle Events

Slide 27

Slide 27 text

Web Browser AWS IoT Topics AWS IoT Rules chat/in/${iot:ClientId} chat/out chat/pub/${room} chat/stream $aws/events/# Each client has a secure “input” topic to receive content from the back end All client can publish on an “output” topic, they are recognizable by their clientId All client can subscribe and receive from “public” topics Another “output” topic optimized for high volumes AWS IoT Lifecycle Events Lambda function to process important messages, such as a new client connection Republish rule to send messages to the corresponding room public topic Lambda function to process high volume dreaming data Kinesis Stream to manage high volume streaming data Lambda function to process AWS IoT Lifecycle Events Store all messages in a database, to be sent to the client on connection

Slide 28

Slide 28 text

Web Browser AWS IoT Topics AWS IoT Rules chat/in/${iot:ClientId} chat/out chat/pub/${room} chat/stream $aws/events/# Each client has a secure “input” topic to receive content from the back end All client can publish on an “output” topic, they are recognizable by their clientId All client can subscribe and receive from “public” topics Another “output” topic optimized for high volumes AWS IoT Lifecycle Events Lambda function to process important messages, such as a new client connection Republish rule to send messages to the corresponding room public topic Lambda function to process high volume dreaming data Kinesis Stream to manage high volume streaming data Lambda function to process AWS IoT Lifecycle Events Store all messages in a database, to be sent to the client on connection You can use this topic to inject JavaScript code in the browser

Slide 29

Slide 29 text

So how does the flow look like?

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

Demo https://chat.danilop.net/websummit

Slide 38

Slide 38 text

Code https://github.com/danilop/serverless-chat More Info http://docs.aws.amazon.com/iot/latest/developerguide/protocols.html http://docs.aws.amazon.com/iot/latest/developerguide/life-cycle-events.html http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB/DocumentClient.html

Slide 39

Slide 39 text

From Event-Driven Architectures…

Slide 40

Slide 40 text

…To Functional Programming?

Slide 41

Slide 41 text

Functional Programming Transforming Data Using Expressions (Functions) Without Side Effects Immutable Data Pure Functions Higher-Order Functions From “Research Topics in Functional Programming” ed. D. Turner, Addison-Wesley, 1990, pp 17–42. 1 Why Functional Programming Matters John Hughes The University, Glasgow Abstract As software becomes more and more complex, it is more and more important to structure it well. Well-structured software is easy to write and to debug, and provides a collection of modules that can be reused to reduce future programming costs. In this paper we show that two fea- tures of functional languages in particular, higher-order functions and lazy evaluation, can contribute significantly to modularity. As examples, we manipulate lists and trees, program several numerical algorithms, and im- plement the alpha-beta heuristic (an algorithm from Artificial Intelligence used in game-playing programs). We conclude that since modularity is the key to successful programming, functional programming o↵ers important advantages for software development. 1 Introduction This paper is an attempt to demonstrate to the larger community of (non- functional) programmers the significance of functional programming, and also to help functional programmers exploit its advantages to the full by making it clear what those advantages are. Functional programming is so called because its fundamental operation is the application of functions to arguments. A main program itself is written as a function that receives the program’s input as its argument and delivers the program’s output as its result. Typically the main function is defined in terms of other functions, which in turn are defined in terms of still more functions, until at the bottom level the functions are language primitives. All of these functions are much like ordinary mathematical functions, and in this paper they will be 1 An earlier version of this paper appeared in the The Computer Journal, 32(2):98–107, April 1989. Copyright belongs to The British Computer Society, who grant permission to copy for educational purposes only without fee provided the copies are not made for direct commercial advantage and this BCS copyright notice appears. https://www.cs.kent.ac.uk/people/staff/dat/miranda/whyfp90.pdf

Slide 42

Slide 42 text

Let’s build a “Tag Cloud” from Your Pictures images

Slide 43

Slide 43 text

getLabels groupBy + renderHtml images Amazon Rekognition browser Event-Driven Architecture Let’s build a “Tag Cloud” from Your Pictures

Slide 44

Slide 44 text

renderHtml(groupBy(getLabels([images])), htmlParams) Functional View Let’s build a “Tag Cloud” from Your Pictures

Slide 45

Slide 45 text

renderHtml(groupBy(getLabels([images])), htmlParams) Functional View Let’s build a “Tag Cloud” from Your Pictures

Slide 46

Slide 46 text

renderHtml(groupBy(getLabels([images])), htmlParams) Functional View Let’s build a “Tag Cloud” from Your Pictures

Slide 47

Slide 47 text

renderHtml(groupBy(getLabels([images])), htmlParams) Functional View Let’s build a “Tag Cloud” from Your Pictures

Slide 48

Slide 48 text

map(f, [x1, x2, …, xn]) = [f(x1), f(x2), …, f(xn)] Higher-Order Functions filter(f, [x1, x2, …, xn]) = [xi if f(xi) is true] count([a, b, a, c, a, b]) = {a: 3, b: 2, c: 1}

Slide 49

Slide 49 text

renderHtml(groupBy(getLabels([images])), htmlParams) ⇩ renderHtml(count(map(getLabel, [images]))), htmlParams) Reusable More reusable

Slide 50

Slide 50 text

Lambda Functions + Step Functions Lambda Function Input State Machine Output translate create execute Tasks State passing (Immutable Data) Tasks are performed only if required (Lazy Evaluation) A Lambda Function dynamically creating a State Machine executing the logic

Slide 51

Slide 51 text

Event-Driven Architectures + Functional Programming + Standard Serverless Library Happy to get your feedback on this!

Slide 52

Slide 52 text

What is Serverless? “Build and run applications without thinking about servers”

Slide 53

Slide 53 text

https://bit.ly/devworkshops

Slide 54

Slide 54 text

© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Danilo Poccia, Technical Evangelist [email protected] Serverless by Example: Building A Real-Time Chat System @danilop danilop