From Big Band Web App to Serverless Bebop

from
Big Band Web App
to
Serverless
Bebop
@AnjanaVakil JazzCon.Tech 2018

Hello!
I’m @AnjanaVakil
Recurse Center Non-Graduate
Mozilla TechSpeaker & Outreachy Alumna
Engineering Learning & Development Lead, Mapbox

location data platform for developers
maps, search, navigation
web, iOS, Android, Unity...

we use to
◍ get user stats
◍ monitor/test unpacker
uploads
◍ ask yoda who’s on call
◍ see who’s out tmrw
◍ pick a random teammate
Place your screenshot here

user-
limits
out
unpackeryoda
stats
Express
slack i/o
auth
our slack-commands app
node

codebase
slack-commands/
├─ readme.md
├─ cloudformation/ #app & cmd config
│ └─ slack-commands.template.js
├─ index.js #express app
├─ commands/
│ ├─ out.js
│ ├─ stats.js
│ └─ ...
└─ test/
├─ index.test.js
├─ out.test.js
├─ stats.test.js
└─ ...

All commands in a single app: Downsides
Security
◍ Permissions?
Secrets?
◍ Least privilege
Maintenance
◍ Many different
teams involved
◍ Ownership?
Support?
◍ Code gumbo
Cost
◍ Always running
◍ No per-command
breakdown

enough
about computers
let’s talk about jazz

“
While swing music tended to feature
orchestrated big band arrangements,
bebop music highlighted improvisation.
wikipedia

Big Band
Glenn Miller Orchestra, c. 1940

Big Band
out unpacker
status
yoda
Express
slack i/o
auth
user-
limits

“I kept thinking there's bound to be something
else. I could hear it sometimes. I couldn't play it....
I found that by using the higher intervals of a
chord as a melody line and backing them with
appropriately related changes, I could play the
thing I'd been hearing. It came alive.
- Charlie Parker
wikipedia

Bebop
Tommy Potter, Charlie Parker, Max Roach, Miles Davis, & Duke Jordan, NYC c. 1945

“As bebop was not intended for dancing, it
enabled the musicians to play at faster tempos.
Bebop musicians explored advanced harmonies,
complex syncopation, altered chords, extended
chords, chord substitutions, asymmetrical
phrasing, and intricate melodies.
wikipedia

Bebop
out
unpacker
status
yoda user-limits

“there’s bound to be something else”
◍ Assign a single owner/gatekeeper?
◍ Multiple single-command apps?
◍ Separate commands from router app

“serverless” functions to the rescue
AWS Lambda

what do you mean “serverless”
Actual Server
You own a computer
You put code on it
You run it constantly
(and you pay constantly)
You keep it healthy
Cloud Server
AWS owns a computer (or 2)
You put code on it
AWS runs it constantly
(and you pay constantly)
You tell AWS how to keep
it healthy
“No” Server
AWS owns a computer
You put code on it
AWS runs it when you ask
(and you pay only then)
AWS keeps it healthy

◍ Only concern: Input -> Output
◍ No state maintained between calls
◍ Can be side-effecting, though
(e.g. API call, database write)
◍ Limited resources & exec time (5m)
what do you mean “function”

Lose the server if it’s...
◍ small
◍ short-lived
◍ self-contained
◍ needed occasionally
to lambda or not to lambda
Keep the server if it’s...
◍ heavy
◍ long-running
◍ interdependent
◍ needed constantly

HTTP API
endpoint
AWS
load
balancerEC2s on ECS
JS
JSJS
old architecture

HTTP API
endpoint
router
new architecture
stats
out
unpacker
yoda

old
codebase
slack-commands/
├─ readme.md
├─ cloudformation/ #app & cmd config
├─ index.js #express app code
├─ commands/ #cmd code
│ ├─ out.js
│ ├─ stats.js
│ └─ ...
└─ test/ #app & cmd tests
├─ index.test.js
├─ out.test.js
├─ stats.test.js
└─ ...

new
codebase
slack-commands/
├─ readme.md
├─ cloudformation/ #app config
├─ index.js #express app code
├─ commander.js #invoke lambdas
└─ test/
├─ commander.test.js
└─ index.test.js
slack-command-{cmd}/
├ readme.md
├ cloudformation/ #cmd config
│ └ slack-command-{cmd}.template.js
├ index.js #cmd code
└ test/
└ index.test.js@AnjanaVakil JazzCon.Tech 2018

what does a
function
look like?

Place your screenshot here
user stats commmand

module.exports.command = (event, context, callback) => {
const { ApiCoreUrl, MapboxToken } = process.env;
const user = event.args[0];
const from = new Date(event.args[1] || (+new Date - 864e5*30)); // 30d
const to = new Date(event.args[2] || (+new Date));
if (isNaN(from)||isNaN(to)) return callback(new Error('invalid date'));
const requrl = getStatsUrl(user, from, to, ApiCoreUrl, MapboxToken);
request(requrl, (err, res, body) => {
if (err||res.statusCode !== 200) return callback(err||res.statusCode);
try { const data = JSON.parse(body); }
catch(err) { return callback(err); }
return callback(null, formatStatsMessage(user, data));
});
}

});
}
handler function
(we tell Lambda its name)

});
}
execution environment
we can configure

});
}
input { args: [ “vakila”, “1/1”, “3/22”] }

});
}
aws runtime info
(e.g. time remaining - ignored here)

});
}
“ok, I’m done” function
(AWS passes this when executing)
error data

we wrote a function!
yay

do we get it up there?
how

Cloud::Formation templates
◍ JSON template - “just code”
◍ define your AWS stack components
◍ upload -> AWS builds your stack

{
"AWSTemplateFormatVersion": "2010-09-09",
"Description": "slack-command-stats",
"Parameters": { "ApiCoreUrl": {...}, "MapboxToken": {...}
"Resources": {
"Command": {
"Type": "AWS::Lambda::Function",
"Properties": {...}
},
"CommandRole": {
"Type": "AWS::IAM::Role",
"Properties": {...}
}
},
"Outputs": { ... }
}

{
"Resources": {
"Command": {
"Properties": {...}
},
"CommandRole": {
"Properties": {...}
}
},
"Outputs": { ... }
}
stack
input
params

{
"Resources": {
"Command": {
"Properties": {...}
},
"CommandRole": {
"Properties": {...}
}
},
"Outputs": { ... }
}
aws
permissions
for function

{
"Resources": {
"Command": {
"Properties": {...}
},
"CommandRole": {
"Properties": {...}
}
},
"Outputs": { ... }
}
actual
lambda
function
the good stuff

"Command": {
"Properties": {
"FunctionName": "slack-command-stats-production",
"Code": { "S3Bucket": {...}, "S3Key": {...} },
"Handler": "index.command",
"Environment": { "Variables": {
"ApiCoreUrl": { "Ref": "ApiCoreUrl" },
"MapboxToken": { "Ref": "MapboxToken" } } },
"Role": { "Fn::GetAtt": ["CommandRole","Arn"] },
"Runtime": "nodejs4.3", "MemorySize": 128, "Timeout": 60,
"Tags": [ { "Key": "Team", "Value": "EngOps"} ]
}
}

"Command": {
"Properties": {
}
}
function
name
helps find it later

"Command": {
"Properties": {
}
}
code to run
the good stuff

"Command": {
"Properties": {
}
}
execution
environment
can pass in params

"Command": {
"Properties": {
}
}
permissions
from earlier

"Command": {
"Properties": {
}
}
what to run it on
totally not a server

"Command": {
"Properties": {
}
}
arbitrary tags
e.g. who owns this?

Mapbox open-source AWS
helpers
github.com/mapbox/
Command-line tools
lambda-cfn create & deploy Node Lambda functions
cfn-config configure/start/update CFN stacks
JS libraries
cloudfriend easily assemble CFN templates in JS
decrypt-kms-env use secret environment vars

we deployed a function!
yay

do we call it?
how

testing in the AWS console (manually)

in Node with AWS SDK
const AWS = require('aws-sdk');
const runCommand = (req, res, next) => {
const [commandName, ...args] = = req.slackText;
const params = {
FunctionName: `slack-command-${commandName}-production`, // our convention
Payload: JSON.stringify({ args: args }), // the `event` Lambda receives
};
const lambda = new AWS.Lambda({ region: 'us-east-1' });
lambda.invoke(params).promise()
.catch((err) => err.message) // pass on error message as response data
.then((data) => res.json(formatForSlack(data)));
};

why
did we do all that?

Before (single app)
◍ Many secrets in one
stack
◍ Updating your code
updates whole stack
◍ No fine-grained cost
analysis
Refactoring to Lambda: Benefits
After (multiple Lambdas)
◍ Each stack only knows
its own secrets
◍ Updating your code
leaves others untouched
◍ Each stack/fn can be
tagged & cost-monitored

HTTP API
endpoint
router
next steps
stats
out
unpacker
yoda

HTTP API
endpoint
next steps
stats
out
unpacker
yoda
router

Merci!
@AnjanaVakil
anjana@mapbox.com
✌ Team Mapbox
Young Hahn, Emily McAfee,
Kelly Young, Jake Pruitt, Andrew Evans
JazzCon.Tech Organizers
Images from Wikimedia
Template by SlidesCarnival.com

From Big Band Web App to Serverless Bebop

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a From Big Band Web App to Serverless Bebop

Similar a From Big Band Web App to Serverless Bebop (20)

Más de JSFestUA

Más de JSFestUA (20)

Último

Último (20)

From Big Band Web App to Serverless Bebop