Kotlin for backend using serverless + aws lambda
Download as pptx, pdf0 likes114 views
This document discusses using Kotlin for backend development with AWS Lambda and serverless architecture. Some key advantages of Kotlin include its conciseness, type safety, IDE support, and interoperability with Java. AWS Lambda provides horizontal scaling and allows focusing on code without managing servers. The Serverless framework makes it easy to deploy event-driven functions. Some challenges of AWS Lambda include package size limits and cold start times, while the Serverless framework may have longer initial deploy times for large projects. Overall warm up functions and use additional stacks to address resource limits when using these serverless technologies.
More Related Content
What's hot (14)
Similar to Kotlin for backend using serverless + aws lambda (20)
![Serverless Day Zero: How to Serveless [July 2019]](https://cdn.slidesharecdn.com/ss_thumbnails/serverlessdayzerojuly2019-240905073021-36a081b3-thumbnail.jpg?width=560&fit=bounds)
Recently uploaded (20)
Kotlin for backend using serverless + aws lambda
- 1. Kotlin for backend using Serverless + AWS Lambda
- 3. 80/20 rule of why Kotlin - Concise
- 4. 80/20 rule of why Kotlin - Concise
- 5. 80/20 rule of why Kotlin - Concise - Type safety
- 6. 80/20 rule of why Kotlin - Concise - Type safety - Great IDE support
- 7. 80/20 rule of why Kotlin - Concise - Type safety - Great IDE support - Interoperability with Java
- 8. 80/20 rule of why Kotlin - Concise - Type safety - Great IDE support - Interoperability with Java - Minimal learning curve
- 9. 80/20 rule of why Kotlin - Minimal learning curve
- 10. What is AWS Lambda AWS Service that allows you to run code without managing servers
- 12. Why AWS Lambda - Almost free
- 13. Why AWS Lambda - Almost free - Minimal learning curve
- 14. Why AWS Lambda - Almost free - Minimal learning curve - Horizontal scaling by default
- 15. Why AWS Lambda - Horizontal scaling by default
- 16. Why AWS Lambda - Almost free - Minimal learning curve - Horizontal scaling by default - Allows you to focus on your code. No need to manage servers
- 17. What is Serverless framework? The Serverless Framework is a CLI tool that allows users to build & deploy auto- scaling, pay-per-execution, event-driven functions.
- 18. Why Serverless? - Cloud agnostic ( In theory) - Fast set-up
- 19. Fast set-up
- 20. Fast set-up
- 21. Fast set-up
- 22. Why Serverless? - Cloud agnostic ( In theory) - Fast set-up - Minimal learning curve
- 23. Why Serverless? - Cloud agnostic ( In theory) - Fast set-up - Minimal learning curve - Infrastructure code can be managed with your project
- 24. Cons AWS Lambda - If you don’t want to be tied to AWS - Package size limit of 50MB - Has 300 seconds time-out. Not suitable for long running processes i.e image processing, batch etc - You have no control on how your application scale. - Cold Startup issues. Can be fixed by - having a keep-alive function
- 25. Cons AWS Lambda
- 26. Cons AWS Lambda - If you don’t want to be tied to AWS - Package size limit of 50MB - Has 300 seconds time-out. Not suitable for long running processes i.e image processing, batch etc - You have no control on how your application scale. - Cold Startup issues ( Specific to compiled runtime)
- 27. Cons Serverless - As your project get bigger, initial deploy could take some time ( Anecdotal evidence )
- 28. Lessons using AWS lambda and serverless Warm up your functions. Lambda functions , specially those running in compiled runtime have a tendency to have a slow start-up time ( cold start). Solutions : 1. Use warmup plugin https://www.npmjs.com/package/serverless-plugin- warmup 2. Use cloudwatch to ping your functions
- 29. Lessons using AWS lambda and serverless AWS Cloudformation has a 200 resource limit. Solution 1. use https://github.com/SC5/serverless-plugin-additional-stacks 2. Split your APIs to microservices
Editor's Notes
- #3: https://www.reddit.com/r/ProgrammerHumor/comments/8ts8l9/me_rlang/
- #20: Assuming you have JDK and node js set-up. It’s just a matter of installing serverless Running serverless create Configuring credentials Then doing a deploy Install severless Install serverless npm install -g serverless Create function serverless create —-template aws-kotlin-jvm-gradle --path FUNCTION_NAME Configure aws credentials serverless config credentials --provider aws --key YOUR_KEY --secret YOUR_SECRET Deploy ./gradlew deploy
- #21: It would create the boiler plate code for you. Serverless.yml is where you manage your infrastracture An initial handler is created for you inside serverless/handler
- #22: It would create the boiler plate code for you. Serverless.yml is where you manage your infrastracture An initial handler is created for you inside serverless/handler