Serverless architectures on AWS Lambda

@srhtcn Serverless Architectures on AWS Lambda: The Opsgenie Experience Serhat
Can @srhtcn

@srhtcn Who am I? • Ex-Software Engineer Technical Evangelist at
• DevOpsDays core team member • AWS Community Hero • @srhtcn on Twitter

@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.

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.

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.

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 Language support Node.js (JavaScript) Python, Java (Java 8 compatible),
C# (.NET Core) Golang NEW: Bring your own language!

@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: 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 Pricing
(still not a huge concern) 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

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

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

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 Custom integrations AWS Lambda is a life saver for
custom solutions, because; ◦ Customers do not need to manage servers ◦ Easy to get started and deploy (give a .zip file) ◦ Real pay what you use pricing

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

@srhtcn Alert Enrichment

@srhtcn Elasticsearch data indexing

@srhtcn DynamoDB Cross Region Replication

@srhtcn DynamoDB Auto Scale

@srhtcn Service and Incident Management

@srhtcn An incident of $40,000

@srhtcn Lessons learned: An incident of $40,000 Avoid infinite retries
Monitor and alert for pricing (no pricing metric for AWS Lambda) Think of Cloudwatch cost and sample logs & metrics

@srhtcn Challenges • Cold start • Local development • Concurrent
execution limit • No well-known good practices

@srhtcn Concurrent Executions Lambda concurrent execution count for non stream
based events: events (or requests) per second * function duration Hard to deal with peaks in request numbers Takes time to increase the limit Functions affect each other’s scalability

@srhtcn Cold start When: - memory size - code size
- VPC - the language https://read.acloud.guru/does-coding-language-memory-or-package-size-affect-cold-starts-of-aws-lambda-a15e26d12c76

@srhtcn Solving cold start problem Wait for AWS to improve
it Increase memory (and pay more) Lightweight application framework instead of Spring Do some smart warm-up

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

Serverless architectures on AWS Lambda

Serverless architectures on AWS Lambda

More Decks by Serhat Can

Other Decks in Technology

Featured

Transcript