Slide 1

Slide 1 text

#jawspankration2024 What is “Lambdaless” Serverless Masaki Suzuki (PayPay Card Corp.) 2024/08/25 JAWS Pankration 2024

Slide 2

Slide 2 text

#jawspankration2024 Agenda 1. Self-Introduction & Notice 2. Introduction:What is “Lambdaless” Serverless 3. Consideration:Advantages and Disadvantages 4. Summary:Use Cases 2

Slide 3

Slide 3 text

#jawspankration2024 Self-Introduction ◼ Name: Masaki Suzuki ◼ Job: Infrastructure Engineer & DBA at PayPay Card Corp. ◼ AWS Community Builder(Serverless) ※JAWS-UG Nagoya and CDK branch ◼ Like: • AWS(especially Lambda), Serverless backend • Infrastructure as Code(especially AWS CDK), CI/CD (GitHub Actions, AWS CodePipeline) etc. • TypeScript, JavaScript(Node.js), Bun.js ◼ SNS: • @makky12 (SUZUKI Masaki@クラウドエンジニア) • @makky12.bsky.social • https://github.com/smt7174/ • http://makky12.hatenablog.com/ 3

Slide 4

Slide 4 text

#jawspankration2024 Self-Introduction 4 • I contributed an article to the June issue of Software Design, on sale 5/17(Fri). • Authored chapters 1 and 3 of the second section. (featuring Bun.js)

Slide 5

Slide 5 text

#jawspankration2024 Notice ◼ All opinions of this slide is my own. • It‘s not related to the company and any communities I belong. ◼ “AWS” and “Amazon” at the beginning of AWS services are omitted ◼ CloudFormation is written as “CFn” in this slide. (for the reason of character count) 5

Slide 6

Slide 6 text

#jawspankration2024 Introduction:What is “Lambdaless” Serverless

Slide 7

Slide 7 text

#jawspankration2024 What is “Lambdaless” Serverless 7 • “Lambdaless” is one of the thought about Serverless. • This is to eliminate Lambda from process can be done without it. • This is introduced by Daisuke Awaji(AWS SA) at AWS Summit Japan. Not Lambdaless Lambda Function Target Services (ex. S3, DynamoDB, etc.) Event Source (ex. API Gateway) Lambdaless Target Services (ex. S3, DynamoDB, etc.) Event Source (ex. API Gateway) Direct Access

Slide 8

Slide 8 text

#jawspankration2024 Consideration:Merits and Demerits

Slide 9

Slide 9 text

#jawspankration2024 Merits 9 Management and Maintenance of Lambda No need to manage Lambda, test Lambda functions on each changes, and maintain of Lambda runtime (especially, Node.js) Cost reduction Lambdaless can decrease the cost of Lambda and so effective because Lambda exists a lot in application in many cases. . Number of CFn Stack resource Lambdaless also can decrease the number of CFn Stack resource(MAX: 500). As noted at ”Cost reduction”, Lambda exists a lot in application, so it’s so effective.

Slide 10

Slide 10 text

#jawspankration2024 Demerits 10 Limited only simple process Lambdaless can’t be applied at complex process (limited to simple one). For example, in the case of API Gateway, limited to the process can be done by using Mapping Template. Management of Mapping Template To create and manage Mapping Template is not easy. (Lambda Integration is used for resolving it, and it’s so useful.) Problem of no-writing program code No-writing program code may cause a problem that people who don’t familiar with AWS can‘t manage. (If using program code, even them can do to some degree)

Slide 11

Slide 11 text

#jawspankration2024 Summary:Use Cases

Slide 12

Slide 12 text

#jawspankration2024 Summary(Use Cases) 12 • In case of existing many Lambda in application and those processes are simple, Lambdaless may be effective some degree. • I think you don’t need to apply Lambdaless right now. (※1) • When considering applying Lambdaless, I think it's better to focus on the project status(※2) and management rather than cost reduction. • Using Lambda is absolutely not an anti-pattern! (※3) ※1: It seems good to consider when starting to create new application. ※2:Members’ skill, experience, and so on. ※3: Because there are many processes can be done only using Lambda, and Lambda integration is so useful, and more.

Slide 13

Slide 13 text

#jawspankration2024 Thank You! That’s all.