Achieving Continuous Delivery with AWS Lambda and Codeship

Transcription

1 Achieving Continuous Delivery with AWS Lambda and Codeship

2 Timeline Ajay Nair from AWS Introduction to AWS Lambda Florian Motlik from Codeship Introduction to Codeship and Deploying to AWS Lambda Martin Tajur How Pipedrive uses Codeship and AWS Lambda Q&A

3 FAQ We re recording and will share the recording soon after Tweet with #awslambdawebinar Ask questions through GoToWebinar Question UI

4 Introduction to Lambda Ajay Nair

5 First, a little bit about Lambda

6 AWS Lambda COMPUTE SERVICE EVENT DRIVEN Run code without thinking about servers Code only runs when it needs to run

7 AWS Lambda: Benefits SERVERLESS EVENT-DRIVEN SCALE SUBSECOND BILLING

8 AWS Lambda: Capabilities BRING YOUR OWN CODE COMPUTE POWER LEVELS FLEXIBLE INVOCATION PATHS GRANULAR PERMISSIONS CONTROL

9 AWS Lambda: Putting it to work Mobile and Web backends File processing with Amazon S3 Amazon Dynamo DB triggers Microservices with API Gateway Amazon Echo skills AWS CloudFormation custom resources Amazon Kinesis processors Customized notifications with Amazon SNS Amazon Cognito triggers and the list will continue to grow!

10 AWS Lambda: How it works AUTHOR CONFIGURE DEPLOY LOG AND MONITOR

11 Codeship and Lambda Flo Motlik

12 Build - Release Cycle Build Validate Test Release

13 The top lesson that Cockcroft learned at Netflix is that speed wins in the marketplace. If you ask any developer whether a slower development process is better, no one ever says yes.

14 Codeship in a Nutshell

15 AWS Lambda on Codeship

16 { "Version": " ", "Statement": [ { "Effect": "Allow", "Action": [ "lambda:updatefunctioncode", "lambda:updatefunctionconfiguration", "lambda:invokefunction", "lambda:getfunction" ], "Resource": [ "arn:aws:lambda:your_aws_region:your_aws_ac COUNT_ID:function:YOUR_FUNCTION_NAME" ] } ] }

17

18

19 Dockerized Codeship

20 Support any Software???????????

21 Flexible Workflows

22 Parity between local & CI & Production

23 Sign up at

24

25

26

27 How we use AWS Lambda to process incoming s Martin Tajur CTO, Co-Founder

28 Web-based CRM for small teams with big ambitions.

29 Web-based CRM for small teams with big ambitions. Founded in 2010.

30 Web-based CRM for small teams with big ambitions. Founded in Used by well over 10,000 businesses worldwide.

31 Web-based CRM for small teams with big ambitions. Founded in Used by well over 10,000 businesses worldwide employees, venture funded (BVP, Series A in 2015)

32 Web-based CRM for small teams with big ambitions. Founded in Used by well over 10,000 businesses worldwide employees, venture funded (BVP, Series A in 2015) Very end user focused, helping the actual sales person do their job.

33

34

35

36 What we do with Lambda

37 What we do with Lambda TL;DR: We process incoming s in Lambda.

38 What we do with Lambda

39 What we do with Lambda Gmail

40 What we do with Lambda Gmail Receive

41 What we do with Lambda Gmail Receive Process

42 What we do with Lambda Gmail Receive Process Store

43 What we do with Lambda Gmail Receive Process Store We process incoming s in Lambda.

44

45 Pipedrive Gmail integration Work with your deals and contacts straight in the CRM

46 Pipedrive Gmail integration Work with your deals and contacts straight in the CRM Send and receive s within the CRM

47 Pipedrive Gmail integration Work with your deals and contacts straight in the CRM Send and receive s within the CRM Contact history stored

48 Pipedrive Gmail integration Work with your deals and contacts straight in the CRM Send and receive s within the CRM Contact history stored No juggling between apps

49 Pipedrive Gmail integration Work with your deals and contacts straight in the CRM Send and receive s within the CRM Contact history stored No juggling between apps Keep your focus

50 Pipedrive Gmail integration Work with your deals and contacts straight in the CRM Send and receive s within the CRM Contact history stored No juggling between apps Keep your focus Close more deals

51 Pipedrive Gmail integration Work with your deals and contacts straight in the CRM Send and receive s within the CRM Contact history stored No juggling between apps Keep your focus Close more deals $$$

52 Our Lambda function

53 Our Lambda function Called mail-message-parser

54 Our Lambda function Called mail-message-parser Node.js, Javascript based application

55 Our Lambda function Called mail-message-parser Node.js, Javascript based application Takes in regular HTML, returns nicer HTML

56 Our Lambda function Called mail-message-parser Node.js, Javascript based application Takes in regular HTML, returns nicer HTML Covered with 105 unit tests

57 Our Lambda function Called mail-message-parser Node.js, Javascript based application Takes in regular HTML, returns nicer HTML Covered with 105 unit tests Deployable zip file is 14MB (includes all npm modules)

58 What we do with Lambda Fix broken HTML s

59 What we do with Lambda Fix broken HTML s Filter out unwanted parts of HTML (<script>, attached event handlers, etc)

60 What we do with Lambda Fix broken HTML s Filter out unwanted parts of HTML (<script>, attached event handlers, etc) Consolidate and localize stylesheets in s

61 We process 300,000 s per day on average

62 We process 300,000 s per day on average of the 4,000 users enrolled to the Gmail sync feature on Pipedrive.

63 Processing incoming s is...

64 Processing incoming s is... Highly fluctuating in volume

65 Processing incoming s is... Highly fluctuating in volume High peak hours (20k+ s per hour), lower on weekends (2k per hour), bursts up to 200 s/sec.

66 Processing incoming s is... Highly fluctuating in volume High peak hours (20k+ s per hour), lower on weekends (2k per hour), bursts up to 200 s/sec. CPU intensive

67 Without Lambda, we d put it to a VM or a container.

68 Without Lambda, we would either...

69 Without Lambda, we would either......provision as much as instances as needed to serve the peak hours Bad. Waste of resources during less busy hours. Est. cost around $150/mo.

70 Without Lambda, we would either......provision as much as instances as needed to serve the peak hours Bad. Waste of resources during less busy hours. Est. cost around $150/mo....set up instances as autoscale group Bad. Complexity. Lots of moving parts to manage. Complex deployments. Est. cost up to $100/mo.

71 Without Lambda, it would cost us $100-$150/month. (At current scale.)

72 Our monthly spend on Lambda?

73 Our monthly spend on Lambda? $8

74 Without Lambda at scale?

75 Without Lambda at scale? 4K users, 300K s/day = $150/month

76 Without Lambda at scale? 4K users, 300K s/day = $150/month 100K users, 7.5M s/day = $3750/month

77 With Lambda at scale?

78 With Lambda at scale? 4K users, 300K s/day = $8/month

79 With Lambda at scale? 4K users, 300K s/day = $8/month 100K users, 7.5M s/day = $200/month

80 Without Lambda, it would take a day or two to set it all up.

81 Lambda production deployment setup through Codeship took us

82 Lambda production deployment setup through Codeship took us 20 minutes.

83 Time spent on scaling it down the road 0 hours.

84 How we deploy to Lambda

85 How we deploy to Lambda GitHub based workflow branch out write code pull request merge repeat

86 How we deploy to Lambda GitHub based workflow branch out write code pull request merge repeat Unit tests executed on each pull and commit on Codeship.

87 How we deploy to Lambda GitHub based workflow branch out write code pull request merge repeat Unit tests executed on each pull and commit on Codeship. Merge to master = production deployment, via Codeship.

88 Works perfectly for us

89 Works perfectly for us 0 hours spent on provisioning VMs, worrying about setting up autoscaling or other fine-tuning.

90 Works perfectly for us 0 hours spent on provisioning VMs, worrying about setting up autoscaling or other fine-tuning. 0 hours spent on configuration management.

91 Works perfectly for us 0 hours spent on provisioning VMs, worrying about setting up autoscaling or other fine-tuning. 0 hours spent on configuration management. $$$ saved on having the resources be provisioned 24/7.

92 Works perfectly for us 0 hours spent on provisioning VMs, worrying about setting up autoscaling or other fine-tuning. 0 hours spent on configuration management. $$$ saved on having the resources be provisioned 24/7. 20 minutes spent on setting up continuous delivery.

93 Works perfectly for us 0 hours spent on provisioning VMs, worrying about setting up autoscaling or other fine-tuning. 0 hours spent on configuration management. $$$ saved on having the resources be provisioned 24/7. 20 minutes spent on setting up continuous delivery. Developers can focus on the parser, not the deployment or supporting tools.

94 Thank you. Martin on Twitter With this promo code CODESHIPROCKS 2 months free

95 Q&A Ajay Nair Florian Motlik Martin Tajur