Going Serverless

Serverless is a new framework that allows developers to easily harness AWS Lambda and Api Gateway to build and deploy full fledged API services without needing to deal with any ops level overhead or paying for servers when they're not in use. It's kinda like Heroku on-demand for single functions.

Transcript

1. Going Serverless @jagthedrummer - OctoLabs.com/railsconf2016
2. ! ! @jagthedrummer - OctoLabs.com/railsconf2016
3. Serverless? @jagthedrummer - OctoLabs.com/railsconf2016
4. Serverless @jagthedrummer - OctoLabs.com/railsconf2016
5. @jagthedrummer - OctoLabs.com/railsconf2016
6. ⚡ serverless.com ⚡ framework for building web, mobile and IoT applications exclusively on AWS Lambda, API Gateway, and related services @jagthedrummer - OctoLabs.com/railsconf2016
7. ! ! @jagthedrummer - OctoLabs.com/railsconf2016
8. Vendor Lock-in ! @jagthedrummer - OctoLabs.com/railsconf2016
9. OPS @jagthedrummer - OctoLabs.com/railsconf2016
10. Scale @jagthedrummer - OctoLabs.com/railsconf2016
11. Money @jagthedrummer - OctoLabs.com/railsconf2016
12. Jeremy Green Consultant, Author, SaaSer @jagthedrummer jeremy@octolabs.com @jagthedrummer - OctoLabs.com/railsconf2016
13. IndependentConsultingManual.com Remarq.io Other Interests: Drumming, Photography, and Brewing @jagthedrummer - OctoLabs.com/railsconf2016
14. clickfunnels.com @jagthedrummer - OctoLabs.com/railsconf2016
15. @jagthedrummer - OctoLabs.com/railsconf2016
16. The Pieces @jagthedrummer - OctoLabs.com/railsconf2016
17. Lambda @jagthedrummer - OctoLabs.com/railsconf2016
18. API Gateway @jagthedrummer - OctoLabs.com/railsconf2016
19. DynamoDB @jagthedrummer - OctoLabs.com/railsconf2016
20. RDS @jagthedrummer - OctoLabs.com/railsconf2016
21. CloudFormation @jagthedrummer - OctoLabs.com/railsconf2016
22. Putting it all together @jagthedrummer - OctoLabs.com/railsconf2016
23. @jagthedrummer - OctoLabs.com/railsconf2016
24. @jagthedrummer - OctoLabs.com/railsconf2016
25. @jagthedrummer - OctoLabs.com/railsconf2016
26. @jagthedrummer - OctoLabs.com/railsconf2016
27. Coding in the browser? @jagthedrummer - OctoLabs.com/railsconf2016
28. ! → " → # @jagthedrummer - OctoLabs.com/railsconf2016
29. Serverless to the rescue serverless.com Manage Lambda, API Gateway and CloudFormation via code and CLI instead of via GUI. docs.serverless.com @jagthedrummer - OctoLabs.com/railsconf2016
30. Getting started @jagthedrummer - OctoLabs.com/railsconf2016
31. First step → Create a new AWS account! → Srsly! @jagthedrummer - OctoLabs.com/railsconf2016
32. $ npm install -g serverless @jagthedrummer - OctoLabs.com/railsconf2016
33. $ sls project create @jagthedrummer - OctoLabs.com/railsconf2016
34. _______ __ | _ .-----.----.--.--.-----.----| .-----.-----.-----. | |___| -__| _| | | -__| _| | -__|__ --|__ --| |____ |_____|__| \___/|_____|__| |__|_____|_____|_____| | | | The Serverless Application Framework | | serverless.com, v0.5.5 `-------' @jagthedrummer - OctoLabs.com/railsconf2016
35. Serverless: Initializing Serverless Project... Serverless: Enter a name for this project: (serverless-bkqhpg) going-serverless-demo @jagthedrummer - OctoLabs.com/railsconf2016
36. Serverless: Enter a new stage name for this project: (dev) @jagthedrummer - OctoLabs.com/railsconf2016
37. Serverless: For the "dev" stage, do you want to use an existing Amazon Web Services profile or create a new one? > Existing Profile Create A New Profile Serverless: Select a profile for your project: > lambdatest Serverless: Creating stage "dev"... @jagthedrummer - OctoLabs.com/railsconf2016
38. Serverless: Select a new region for your stage: > us-east-1 us-west-2 eu-west-1 eu-central-1 ap-northeast-1 Serverless: Creating region "us-east-1" in stage "dev"... @jagthedrummer - OctoLabs.com/railsconf2016
39. Serverless: Deploying resources to stage "dev" in region "us-east-1" via Cloudformation (~3 minutes)... Serverless: Successfully deployed "dev" resources to "us-east-1" Serverless: Successfully created region "us-east-1" within stage "dev" Serverless: Successfully created stage "dev" Serverless: Successfully initialized project "going-serverless-demo" @jagthedrummer - OctoLabs.com/railsconf2016
40. $ cd going-serverless-demo $ tree . ├── admin.env # AWS Profiles - gitignored ├── package.json # npm package file ├── s-project.json # project and author data ├── s-resources-cf.json # CloudFormation template └── _meta # meta data for stage/regions config and variables - gitignored ├── resources │ └── s-resources-cf-dev-useast1.json └── variables ├── s-variables-common.json ├── s-variables-dev-useast1.json └── s-variables-dev.json 3 directories, 8 files @jagthedrummer - OctoLabs.com/railsconf2016
41. What should we build? @jagthedrummer - OctoLabs.com/railsconf2016
42. Let's build something real* @jagthedrummer - OctoLabs.com/railsconf2016
43. LPaaS left-pad as a service* * OK, "real" ! @jagthedrummer - OctoLabs.com/railsconf2016
44. $ sls function create left-pad @jagthedrummer - OctoLabs.com/railsconf2016
45. Serverless: Please, select a runtime for this new Function > nodejs4.3 python2.7 nodejs (v0.10, soon to be deprecated) @jagthedrummer - OctoLabs.com/railsconf2016
46. Serverless: For this new Function, would you like to create an Endpoint, Event, or just the Function? > Create Endpoint Create Event Just the Function... Serverless: Successfully created function: "left-pad" @jagthedrummer - OctoLabs.com/railsconf2016
47. $ tree left-pad/ left-pad/ ├── event.json # sample event for testing function locally ├── handler.js # function handler └── s-function.json # data for your lambda function, endpoints and event sources 0 directories, 3 files @jagthedrummer - OctoLabs.com/railsconf2016
48. ! it! @jagthedrummer - OctoLabs.com/railsconf2016
49. $ sls dash deploy @jagthedrummer - OctoLabs.com/railsconf2016
50. $ sls dash deploy _______ __ | _ .-----.----.--.--.-----.----| .-----.-----.-----. | |___| -__| _| | | -__| _| | -__|__ --|__ --| |____ |_____|__| \___/|_____|__| |__|_____|_____|_____| | | | The Serverless Application Framework | | serverless.com, v0.5.5 `-------' Serverless: Select the assets you wish to deploy: left-pad * function - left-pad * endpoint - left-pad - GET - - - - - > Deploy Cancel @jagthedrummer - OctoLabs.com/railsconf2016
51. Serverless: Deploying the specified functions in "dev" to the following regions: us-east-1 Serverless: ------------------------ Serverless: Successfully deployed the following functions in "dev" to the following regions: Serverless: us-east-1 ------------------------ Serverless: left-pad (going-serverless-demo-left-pad): arn:aws:lambda:us-east-1:852612687751:function:going-serverless-demo-left-pad:dev Serverless: Deploying endpoints in "dev" to the following regions: us-east-1 Serverless: Successfully deployed endpoints in "dev" to the following regions: Serverless: us-east-1 ------------------------ Serverless: GET - left-pad - http://serverless.octolabs.com/left-pad @jagthedrummer - OctoLabs.com/railsconf2016
52. @jagthedrummer - OctoLabs.com/railsconf2016
53. Anatomy of a Lambda Function @jagthedrummer - OctoLabs.com/railsconf2016
54. left-pad/handler.js 'use strict'; module.exports.handler = function(event, context, cb) { return cb(null, { message: 'Go Serverless! Your Lambda function executed successfully!' }); }; @jagthedrummer - OctoLabs.com/railsconf2016
55. event used to pass data to the function { string: 'test', padding: 10 } @jagthedrummer - OctoLabs.com/railsconf2016
56. context provides runtime information { getRemainingTimeInMillis: function(){}, functionName: 'handler', functionVersion: 'xyz', awsRequestId: '12345', identity: {...}, clientContext: {...} } @jagthedrummer - OctoLabs.com/railsconf2016
57. callback used to return data or an error // signature callback(error,data); // call with error callback("some error message"); //or call with data callback(null, someData); @jagthedrummer - OctoLabs.com/railsconf2016
58. $ cd left-pad $ npm init ... $ npm install left-pad --save @jagthedrummer - OctoLabs.com/railsconf2016
59. left-pad/handler.js let leftpad = require('left-pad'); module.exports.handler = function(event, context, cb) { }; @jagthedrummer - OctoLabs.com/railsconf2016
60. left-pad/handler.js let leftpad = require('left-pad'); module.exports.handler = function(event, context, cb) { var string = event.string || "", padding = event.padding || 0, }; @jagthedrummer - OctoLabs.com/railsconf2016
61. left-pad/handler.js let leftpad = require('left-pad'); module.exports.handler = function(event, context, cb) { var string = event.string || "", padding = event.padding || 0, paddedString = leftpad(string,padding), payload = { paddedString }; }; @jagthedrummer - OctoLabs.com/railsconf2016
62. left-pad/handler.js let leftpad = require('left-pad'); module.exports.handler = function(event, context, cb) { var string = event.string || "", padding = event.padding || 0, paddedString = leftpad(string,padding), payload = { paddedString }; return cb(null, payload); }; @jagthedrummer - OctoLabs.com/railsconf2016
63. left-pad/s-function.json (simplified) { "runtime": "nodejs4.3", "handler": "handler.handler", "memorySize": 1024 "endpoints": [ ] } @jagthedrummer - OctoLabs.com/railsconf2016
64. left-pad/s-function.json (simplified) { "runtime": "nodejs4.3", "handler": "handler.handler", "memorySize": 1024 "endpoints": [ { "path": "left-pad", "method": "GET", "requestTemplates": { "application/json": { } } } ] } @jagthedrummer - OctoLabs.com/railsconf2016
65. left-pad/s-function.json (simplified) { "runtime": "nodejs4.3", "handler": "handler.handler", "memorySize": 1024 "endpoints": [ { "path": "left-pad", "method": "GET", "requestTemplates": { "application/json": { "string": "$input.params('string')", "padding": "$input.params('padding')" } } } ] } @jagthedrummer - OctoLabs.com/railsconf2016
66. $ sls dash deploy ... Serverless: GET - left-pad - http://serverless.octolabs.com/left-pad @jagthedrummer - OctoLabs.com/railsconf2016
67. http://serverless.octolabs.com/left-pad? string=test&padding=10 { "paddedString":" test" } @jagthedrummer - OctoLabs.com/railsconf2016
68. Testing $ npm install -g mocha $ npm install --save-dev chai @jagthedrummer - OctoLabs.com/railsconf2016
69. left-pad/handler_test.js var expect = require("chai").expect; var handler = require("./handler.js"); describe('handler', function(){ it('returns the right thing', function(){ }); }); @jagthedrummer - OctoLabs.com/railsconf2016
70. left-pad/handler_test.js var expect = require("chai").expect; var handler = require("./handler.js"); describe('handler', function(){ it('returns the right thing', function(){ var event = { string: 'test', padding: 10 }; }); }); @jagthedrummer - OctoLabs.com/railsconf2016
71. left-pad/handler_test.js var expect = require("chai").expect; var handler = require("./handler.js"); describe('handler', function(){ it('returns the right thing', function(){ var event = { string: 'test', padding: 10 }; var context = {}; }); }); @jagthedrummer - OctoLabs.com/railsconf2016
72. left-pad/handler_test.js var expect = require("chai").expect; var handler = require("./handler.js"); describe('handler', function(){ it('returns the right thing', function(){ var event = { string: 'test', padding: 10 }; var context = {}; var cb = function(error, response){ expect(error).to.be.null; expect(response.paddedString).to.equal(" test"); }; }); }); @jagthedrummer - OctoLabs.com/railsconf2016
73. left-pad/handler_test.js var expect = require("chai").expect; var handler = require("./handler.js"); describe('handler', function(){ it('returns the right thing', function(){ var event = { string: 'test', padding: 10 }; var context = {}; var cb = function(error, response){ expect(error).to.be.null; expect(response.paddedString).to.equal(" test"); }; handler.handler(event, context, cb); }); }); @jagthedrummer - OctoLabs.com/railsconf2016
74. $ mocha handler_test.js handler ✓ returns the right thing 1 passing (9ms) @jagthedrummer - OctoLabs.com/railsconf2016
75. What about Ruby? @jagthedrummer - OctoLabs.com/railsconf2016
76. mruby-hello-world$ tree . . ├── event.json ├── handler.js ├── handler.rb # A ruby script! :D ├── mruby # The mruby executable └── s-function.json 0 directories, 5 files @jagthedrummer - OctoLabs.com/railsconf2016
77. mruby-hello-world/handler.js var spawn = require('child_process').spawn; module.exports.handler = function(event, context, callback) { var child = spawn('./mruby', ['handler.rb', JSON.stringify(event, null, 2)]); } @jagthedrummer - OctoLabs.com/railsconf2016
78. mruby-hello-world/handler.js var spawn = require('child_process').spawn; module.exports.handler = function(event, context, callback) { var child = spawn('./mruby', ['handler.rb', JSON.stringify(event, null, 2)]); var rubyOutput = []; child.stdout.on('data', function (data) { rubyOutput.push(data.toString()); }); child.stderr.on('data', function (data) { rubyOutput.push(data.toString()); }); } @jagthedrummer - OctoLabs.com/railsconf2016
79. mruby-hello-world/handler.js var spawn = require('child_process').spawn; module.exports.handler = function(event, context, callback) { var child = spawn('./mruby', ['handler.rb', JSON.stringify(event, null, 2)]); var rubyOutput = []; child.stdout.on('data', function (data) { rubyOutput.push(data.toString()); }); child.stderr.on('data', function (data) { rubyOutput.push(data.toString()); }); child.on('close', function (code) { callback(null,{ message: "We're back from ruby land", rubyOutput: rubyOutput }); }); } @jagthedrummer - OctoLabs.com/railsconf2016
80. mruby-hello-world/handler.rb puts 'Hello, Lambda from Ruby!' puts ARGV @jagthedrummer - OctoLabs.com/railsconf2016
81. http://serverless.octolabs.com/mruby-hello-world { "message":"We're back from ruby land", "rubyOutput":["Hello, Lambda from Ruby!\n[\"{}\"]\n"] } @jagthedrummer - OctoLabs.com/railsconf2016
82. This is not production ready! @jagthedrummer - OctoLabs.com/railsconf2016
83. How fast is all of this? @jagthedrummer - OctoLabs.com/railsconf2016
84. API Gateway Latency @jagthedrummer - OctoLabs.com/railsconf2016
85. Remote API call timing comparison @jagthedrummer - OctoLabs.com/railsconf2016
86. Lambda timing comparison @jagthedrummer - OctoLabs.com/railsconf2016
87. Wrapping Up @jagthedrummer - OctoLabs.com/railsconf2016
88. AWS Provides the Building Blocks @jagthedrummer - OctoLabs.com/railsconf2016
89. Serverless Provides Structure and Process @jagthedrummer - OctoLabs.com/railsconf2016
90. You provide the @jagthedrummer - OctoLabs.com/railsconf2016
91. Thank you! (And thanks to Click Funnels) octolabs.com/railsconf2016 @jagthedrummer - OctoLabs.com/railsconf2016
92. Bonus Slides @jagthedrummer - OctoLabs.com/railsconf2016
93. Lambda Pricing ! Charged by: → # of requests → length of execution @jagthedrummer - OctoLabs.com/railsconf2016
94. Lambda Request Pricing First 1 million requests per month are free $0.20 per 1 million requests thereafter ($0.0000002 per request) @jagthedrummer - OctoLabs.com/railsconf2016
95. Lambda Execution Pricing First 400,000 GB-seconds per month are free $0.00001667 for per GB-second thereafter @jagthedrummer - OctoLabs.com/railsconf2016
96. GB-second = LambdaMemoryInGigabytes * ExecutionTime 1GB * 1sec = 1 GB-sec 0.5GB * 2sec = 1 GB-sec 0.5GB * 0.5sec * 4executions = 1 GB-sec @jagthedrummer - OctoLabs.com/railsconf2016
97. Lambda Pricing Example 3 million executions per month 512MB of memory 1 second execution time $18.74 per month @jagthedrummer - OctoLabs.com/railsconf2016
98. Lambda Pricing Example 3 million executions per month 512MB of memory 0.5 second execution time $6.24 per month @jagthedrummer - OctoLabs.com/railsconf2016
99. Lambda Pricing Example 3 million executions per month 512MB of memory 0.2 second execution time $0.40 per month @jagthedrummer - OctoLabs.com/railsconf2016
100. Lambda Lifecycle ! 1. You upload your code 2. Amazon doesn't do anything @jagthedrummer - OctoLabs.com/railsconf2016
101. Lambda Cold Start ❄ 1. AWS Receives Execution Request 2. Container is provisioned 3. Container is loaded with your code 4. Your code begins execution 5. Your code returns a result @jagthedrummer - OctoLabs.com/railsconf2016
102. Time Passes ! (But not too much) @jagthedrummer - OctoLabs.com/railsconf2016
103. Lambda Container Reuse 㿃 1. AWS Receives Execution Request 2. Your code begins execution 3. Your code returns a result @jagthedrummer - OctoLabs.com/railsconf2016
104. Possible Architectures → Monolithic → Microservices → Nanoservices @jagthedrummer - OctoLabs.com/railsconf2016
105. Monolithic Architecture → A single Lambda handles multiple concerns → Multiple API Gateway endpoints map to one Lambda → Cold start will be slow @jagthedrummer - OctoLabs.com/railsconf2016
106. Microservices Architecture → A single Lambda function for each concern/ resource → Multiple API Gateway enpoints map to multiple Lambdas → Cold start not as slow @jagthedrummer - OctoLabs.com/railsconf2016
107. Nanoservices Architecture → A single Lambda function for each logical function → One-to-one mapping between API Gateway & Lambda → Fastest cold start @jagthedrummer - OctoLabs.com/railsconf2016