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