@srhtcn Serverless Architectures at AWS Lambda: The Experience Serhat Can @srhtcn

@srhtcn Who am I? ● Ex-Software Engineer Technical Evangelist at OpsGenie ● Speak, code, write on DevOps, On-Call, Incident Response, Serverless ● Co-organizer ○ Serverless Turkey Meetup ○ DevOpsDays İstanbul ○ DevOps Turkey Meetup

@srhtcn Modern incident management platform for operating always-on services ● Plan and prepare for incidents ● Ensure issues are never missed, and the right people are notified ● Gain insights to improve your operational efficiency ● 200+ integrations

@srhtcn You want to run code on cloud. Your options: Bare metal IaaS (VM) CaaS (container) PaaS (app) Serverless (function) More control, more code Less control, less code

@srhtcn Making thoughtful decisions about tools and architecture can help; well-considered constraints can free us from the decisions that aren't bringing us distinguishable benefit. Bridget Kromhout https://queue.acm.org/detail.cfm?id=3185224

@srhtcn What is Serverless?

@srhtcn Defining Serverless Serverless is an event driven, utility based, stateless, code execution environment. Simon Wardley @swardley

@srhtcn Defining Serverless Event driven: Code is initiated and run after an event like HTTP request or storage of a file triggers.

@srhtcn Defining Serverless Event driven: Code is initiated and run after an event like HTTP request or storage of a file triggers. Utility based: No payment for idle time or hosting. You pay for the resources you use when your code is triggered.

@srhtcn Defining Serverless Event driven: Code is initiated and run after an event like HTTP request or storage of a file triggers. Utility based: No payment for idle time or hosting. You pay for the resources you use when your code is triggered. Stateless: Code execution environment is deconstructed after sometime. No information is guaranteed to stay in the environment after function execution is completed.

@srhtcn Defining Serverless Event driven: Code is initiated and run after an event like HTTP request or storage of a file triggers. Utility based: No payment for idle time or hosting. You pay for the resources you use when your code is triggered. Stateless: Code execution environment is deconstructed after sometime. No information is guaranteed to stay in the environment after function execution is completed. Code execution: Just code, not servers / VMs / containers etc.

@srhtcn Why should I go Serverless? Two main reasons

@srhtcn Less is more Less code to maintain, less ops, less toil (work tied to running a production service that tends to be manual, repetitive) - Scaling - Provisioning - OS or Language updates - Resource utilization - Network monitoring - Fault tolerance - Shipping logs https://landing.google.com/sre/book/chapters/eliminating-toil.html

@srhtcn

@srhtcn Economics - No payment for idle time or hosting - Easy to get started - Faster time to market

@srhtcn AWS Lambda

@srhtcn How it works?

@srhtcn How it works internally? https://engineering.opsgenie.com/what-is-different-in-the-serverless-world-b9e0f68de191

@srhtcn Pricing You choose memory size % of CPU core and network capacity increases proportionally with memory More memory doesn’t always mean you pay more

@srhtcn https://www.slideshare.net/ChrisMunns/aws-startup-day-boston-2018-the-best-practices-and-hard-lessons-learned-of-serverless-applications

@srhtcn Supported event sources 20 different services can trigger AWS Lambda functions including. Event sources that aren't stream-based: Synchronous invocation: AWS SDK, Cognito, Alexa, API Gateway Asynchronous invocation: S3, SNS, CloudWatch logs, CloudWatch events Poll-based (or pull model) event sources that are stream-based: Kinesis, DynamoDB Streams Poll-based event sources that are not stream-based: SQS

@srhtcn Toolkit around AWS Lambda Orchestration: Step Functions Deployment: SAM, Serverless.js, CloudFormation, Apex, Terraform Monitoring: Cloudwatch, X-Ray, Thundra Marketplace: AWS Serverless Application Repository

@srhtcn AWS Lambda at OpsGenie AWS Lambda with Java 8 DynamoDB SQS SNS VPC Serverless.js

@srhtcn Fast scaling under immediate high load Under-utilized machines Operational complexity Learning curve - kubernetes? AWS Fargate - YES! Why did we consider AWS Lambda?

@srhtcn OpsGenie’s Serverless journey 2015 Writing small scale custom integrations At this point, we started leveraging AWS Lambda to help our customer run custom code

@srhtcn OpsGenie’s Serverless journey 2015 Writing small scale custom integrations At this point, we started leveraging AWS Lambda to help our customer run custom code First production usage Started using AWS Lambda for leveraging async / not business critical jobs such as DynamoDB autoscale 2016

@srhtcn OpsGenie’s Serverless journey 2015 Writing small scale custom integrations At this point, we started leveraging AWS Lambda to help our customer run custom code First production usage Started using AWS Lambda for leveraging async / not business critical jobs such as DynamoDB autoscale 2016 Service and Incident Management A new customer facing feature running on AWS Lambda integrated with the rest of the code base. 2017

@srhtcn OpsGenie’s Serverless journey 2015 Writing small scale custom integrations At this point, we started leveraging AWS Lambda to help our customer run custom code First production usage Started using AWS Lambda for leveraging async / not business critical jobs such as DynamoDB autoscale 2016 Service and Incident Management A new customer facing feature running on AWS Lambda integrated with the rest of the code base. 2017 A Spinoff: Thundra Observability for AWS Lambda 2018

@srhtcn Fixing “it is slow” is harder in AWS Lambda Too many moving pieces No way to attach an agent Even how to send the monitoring data is a discussion point

@srhtcn Determine the latency in different levels Automatic instrumentation GC, Thread counts & durations, CPU usage details Get the stack trace in case of an error and drill down See logs, traces, and metrics in one view thundra.io What we needed was

@srhtcn Serverless Architectures

@srhtcn Alert Enrichment

@srhtcn DynamoDB Cross Region Replication

@srhtcn DynamoDB Auto Scale

@srhtcn Service and Incident Management

@srhtcn Demo: Create Alerts from Slack Messages Source: https://github.com/opsgenie/slack-to-opsgenie-alert-creator

@srhtcn Thank you! Serhat Can twitter.com/srhtcn linkedin.com/in/serhatcan medium.com/@serhatcan engineering.opsgenie.com