This document discusses serverless computing using the Serverless framework. It begins with an introduction to serverless and examples of serverless services the author has created. It then compares the Serverless framework to other serverless platforms and discusses benefits of serverless such as increased development speed and avoiding vendor lock-in. The document outlines the serverless development process and compares Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It also discusses configuring and deploying Lambda functions using the Serverless framework.

1. Serverless Node.js
npm i serverless -g
- By Cecilia Cho

2. Why How
Discussion

3. Question 1
Have you ever used Serverless or APEX?
https://serverless.com/
http://apex.run/

4. Question 2
Have you ever thought about below concepts?
PaaS BaaS
CaaS SaaS
FaaS IaaS
MaaS XaaS

5. IaaS vs PaaS vs SaaS

6. SaaS
Gmail, Dropbox,
Netflix, Office365,
Facebook
BaaS
Firebase
(storage, Analytics,
Push notifications,
dashboards, social
integration)
Refer to
http://www.hostingadvice.com/how-to/iaas-vs-p
aas-vs-saas/

7. How I met Serverless
Legacy server didn’t have scalability and flexibility.
=> A new system was needed in terms of PaaS
● Serverless Infrastructures I’ve created since 2017
1. IOTPKG1.6 service server
2. Proxy server (between Legacy and IOTPKG1.6)
3. RMS (Hotel room management system)
4. Chatbot Ext + Chatbot Log

8. Serverless Framework vs Event Gateway
Function as a ServicePlatform as a Service

9. WHY Serverless?
1. Quick & easy Deploy, less code
2. Low Maintenance cost
3. Lambda local test & debugging(breaking point)
4. NPM Plugin
5. Cross-Cloud

10. Benefits of the Serverless
● Increase development speed - The Serverless Framework CLI enables developers to build, test, and
deploy all in the same environment. Developers write their functions in cloud-agnostic Serverless YAML,
and services can be deployed with a single command. Transactionally deploy code to multiple
providers, version your deployments, and roll back the deployment if necessary.
● Avoid vendor lock-in - Different cloud providers all have different required formats and deployment
methods.
● Infrastructure as Code - Configure infrastructure across multiple clouds.
● Existing ecosystem - The Serverless Framework is pluggable, and many dozens of
community-contributed plugins exist in our GitHub Plugins repo.

11. Configurable AWS managed services
API GATEWAY, LAMBDA, S3, DYNAMODB, CloudFormation, CloudWatch, SNS,
Alexa, VPC설정 …
(Lambda warm-up, CloudWatch Log retention, DynamoDB TTL, LSI, GSI ..)
LAMBDA
● Official : NodeJS, Java, and Python
● C#, Go, Swift, Kotlin, Scala

12. Lambda
Cold start 방지 :
● memorysize 1536MB cheaper & faster (https://serverless.com/blog/aws-lambda-power-tuning/)
● warm-up

13. How to develop?
1. Install
2. Configure
3. Coding
4. Packing
5. Local Test
6. Deploy

14. Configure
Serverless.yml
https://{service}.execute-api.{region}.amazonaws.com/{stage}
Provider
Plugin
Package

15. Coding
IDE : WebStorm
Runtime : Node.js 4.3 or 6.10
NPM / plugin (https://github.com/serverless/plugins)
Language : ES6/ES7, TypeScript, CoffeeScript, Kotlin with npm,

16. Packing (interpret, minify, uglify)
Node module
(prod, dev)

17. Local Test
● Break Point
● Command line using ‘Invoke local’
$ sls invoke local --function getSymptomCode --path template/symptom-code-get.json
● Mocha Test (BDD)

19. Deploy
173KB
$ sls deploy

21. Q & A