Two Years, Zero servers: Lessons learned from running a startup 100% on Serverless. By Tal Bereznitskey.
0 likes81 views
Running Highly Available Large Scale Systems is a lot of work. For the past 2.5 years, we've been running 100% serverless on a full production environment, serving customers worldwide. No VMs, no containers, no Kubernetes. Just code. In this session I will present why we decided to go fully serverless at Torii, how it helped us move faster than our competitors, where did serverless computing worked best and where there's more work to be done.
Ad
More Related Content
What's hot (20)
Similar to Two Years, Zero servers: Lessons learned from running a startup 100% on Serverless. By Tal Bereznitskey. (20)
Ad
More from Cloud Native Day Tel Aviv (20)
Ad
Recently uploaded (20)
Two Years, Zero servers: Lessons learned from running a startup 100% on Serverless. By Tal Bereznitskey.
- 1. SERVERLESS LESSONSSERVERLESS LESSONS Running a startup 100% on Serverless
- 2. TAL BEREZNITSKEYTAL BEREZNITSKEY Co-Founder and CTO
- 3. TAL BEREZNITSKEYTAL BEREZNITSKEY Co-Founder and CTO SaaS Management Platform
- 4. TAL BEREZNITSKEYTAL BEREZNITSKEY Co-Founder and CTO built entirely on serverless SaaS Management Platform
- 5. 🤖🤖 1 MINUTE SLACK BOT1 MINUTE SLACK BOT
- 6. CODE - THE UPPER-BOTCODE - THE UPPER-BOT const app = require('express') app.get('/', (req, res) => { const { text = '' } = req.query const uppercase = text.toUpperCase() res.send('Your uppercase text is ' + uppercase) }) app.listen(process.env.PORT)
- 9. DEPLOYDEPLOY $ build: 175 files, 7.4 MB (662ms) deploy: staging (commit c6f180c) (25.522s) stack: complete (14.198s) endpoint: https://2ab05.execute-api.us-east-1.amazonaws.com/staging/ up
- 10. TESTTEST $
- 12. TESTTEST $ Your uppercase text is COMMAND-LINE-TEST curl https://...amazonaws.com/?text=command-line-test
- 14. RESULTRESULT
- 15. WHAT JUST HAPPENED?WHAT JUST HAPPENED?
- 16. UPUP
- 17. WHAT DID WE GET?WHAT DID WE GET? 1. Highly available Slack bot 2. Scales from 0 to Infinity 3. Pay per use 4. No server management
- 18. WHAT DID WE GET?WHAT DID WE GET? 1. Highly available Slack bot 2. Scales from 0 to Infinity 3. Pay per use 4. No server management 5. Awesome Developer Experience!
- 19. 🆒🆒BUT CANBUT CAN SERVERLESSSERVERLESS BE USED FOR “BE USED FOR “REALREAL” WORK ?” WORK ?
- 20. WILLWILL SERVERLESSSERVERLESS WORK FOR OURWORK FOR OUR STARTUP?STARTUP?
- 21. WHY CHOOSE SERVERLESS?WHY CHOOSE SERVERLESS?
- 22. WHY CHOOSE SERVERLESS?WHY CHOOSE SERVERLESS? Minimum ops
- 23. WHY CHOOSE SERVERLESS?WHY CHOOSE SERVERLESS? Focus on delivering more value Minimum ops
- 24. WHY CHOOSE SERVERLESS?WHY CHOOSE SERVERLESS? Advantage over competition Minimum ops Focus on delivering more value
- 25. WHY CHOOSE SERVERLESS?WHY CHOOSE SERVERLESS? Win Minimum ops Focus on delivering more value Advantage over competition
- 26. WHY CHOOSE SERVERLESS?WHY CHOOSE SERVERLESS? ... while sleeping better at night Minimum ops Focus on delivering more value Advantage over competition Win
- 27. SERVERLESS @ TORIISERVERLESS @ TORII API Server(s) Background jobs Static content
- 29. BEST PRACTICES OUT-OF-THE-📦BEST PRACTICES OUT-OF-THE-📦
- 30. BEST PRACTICES OUT-OF-THE-📦BEST PRACTICES OUT-OF-THE-📦 1. Immutability
- 31. BEST PRACTICES OUT-OF-THE-📦BEST PRACTICES OUT-OF-THE-📦 2. Versioning 1. Immutability
- 32. BEST PRACTICES OUT-OF-THE-📦BEST PRACTICES OUT-OF-THE-📦 3. Aliases 1. Immutability 2. Versioning
- 33. BEST PRACTICES OUT-OF-THE-📦BEST PRACTICES OUT-OF-THE-📦 4. Zero downtime deployments 1. Immutability 2. Versioning 3. Aliases
- 34. BEST PRACTICES OUT-OF-THE-📦BEST PRACTICES OUT-OF-THE-📦 5. Instant Rollbacks 1. Immutability 2. Versioning 3. Aliases 4. Zero downtime deployments
- 35. INFRASTRUCTURE-AS-CODEINFRASTRUCTURE-AS-CODE Friendly tools, even I can do it...
- 36. INFRASTRUCTURE-AS-CODEINFRASTRUCTURE-AS-CODE Friendly tools, even I can do it... service: scheduled-cron-example functions: cron: handler: index.handler events: # Invoke Lambda function every minute - schedule: rate(1 minute)
- 38. BETTERBETTER SECURITYSECURITY Automatic OS and runtime security patches
- 39. BETTERBETTER SECURITYSECURITY Permissions per function Automatic OS and runtime security patches
- 40. BETTERBETTER SECURITYSECURITY SSH is dead, less attack vectors Automatic OS and runtime security patches Permissions per function
- 41. BETTERBETTER SECURITYSECURITY Easier certification Automatic OS and runtime security patches Permissions per function SSH is dead, less attack vectors
- 42. LIMITSLIMITS
- 43. LIMITSLIMITS 15 minute max run time.
- 44. LIMITSLIMITS Recursive invocations.15 minute max run time.
- 45. LIMITSLIMITS 30 sec max API Gateway responses. 15 minute max run time. Recursive invocations.
- 46. LIMITSLIMITS Decoupled invocation. 15 minute max run time. Recursive invocations. 30 sec max API Gateway responses.
- 47. LIMITSLIMITS No persistent servers, websockets, polling. 15 minute max run time. Recursive invocations. 30 sec max API Gateway responses. Decoupled invocation.
- 48. LIMITSLIMITS There's a service for that. 15 minute max run time. Recursive invocations. 30 sec max API Gateway responses. Decoupled invocation. No persistent servers, websockets, polling.
- 49. PERFORMANCE - COLD STARTSPERFORMANCE - COLD STARTS
- 50. PERFORMANCE - COLD STARTSPERFORMANCE - COLD STARTS
- 51. OPTIMIZING FUNCTIONSOPTIMIZING FUNCTIONS A lambda function is similar to a website
- 52. OPTIMIZING FUNCTIONSOPTIMIZING FUNCTIONS A lambda function is similar to a website Bundle using Webpack
- 53. OPTIMIZING FUNCTIONSOPTIMIZING FUNCTIONS A lambda function is similar to a website Remove useless files Bundle using Webpack
- 54. OPTIMIZING FUNCTIONSOPTIMIZING FUNCTIONS A lambda function is similar to a website Bundle + Remove Bundle using Webpack Remove useless files
- 55. OPTIMIZING FUNCTIONSOPTIMIZING FUNCTIONS A lambda function is similar to a website Lazy load code Bundle using Webpack Remove useless files Bundle + Remove
- 56. OPTIMIZING FUNCTIONSOPTIMIZING FUNCTIONS A lambda function is similar to a website Open source: , , Bundle using Webpack Remove useless files Bundle + Remove Lazy load code ncc pkg lambdapack
- 57. PERFORMANCE - LATENCYPERFORMANCE - LATENCY
- 58. PERFORMANCE - LATENCYPERFORMANCE - LATENCY
- 59. SCALINGSCALING Functions can scale, can the rest keep up?
- 60. SCALINGSCALING Functions can scale, can the rest keep up? Limit concurrency
- 61. ONE FUNCTION VS. MANYONE FUNCTION VS. MANY
- 62. ONE FUNCTION VS. MANYONE FUNCTION VS. MANY Many small functions or just a large one?
- 63. ONE FUNCTION VS. MANYONE FUNCTION VS. MANY API servers are better as one large function Many small functions or just a large one?
- 64. ONE FUNCTION VS. MANYONE FUNCTION VS. MANY Less cold starts, easier to deploy and test Many small functions or just a large one? API servers are better as one large function
- 65. SECRETSSECRETS
- 66. SECRETSSECRETS AWS Systems Manager Parameter Store (SSM)
- 67. SECRETSSECRETS Decrypt at runtime. AWS Systems Manager Parameter Store (SSM)
- 68. SECRETSSECRETS Doesn't scale well. AWS Systems Manager Parameter Store (SSM) Decrypt at runtime.
- 69. SECRETSSECRETS Bake it during deployment AWS Systems Manager Parameter Store (SSM) Decrypt at runtime. Doesn't scale well.
- 70. LOGGINGLOGGING Loggers were intended for always running servers
- 71. LOGGINGLOGGING Loggers were intended for always running servers Who ❤CloudWatch?
- 72. LOGGINGLOGGING Loggers were intended for always running servers Lambda 👉 CloudWatch 👉 Lambda 👉 Papertrail Who ❤CloudWatch?
- 73. ACTIVELY IMPROVINGACTIVELY IMPROVING We're just at the beginning
- 74. ACTIVELY IMPROVINGACTIVELY IMPROVING We're just at the beginning Cloud providers are investing a lot in serverless
- 75. ACTIVELY IMPROVINGACTIVELY IMPROVING We're just at the beginning Since most infra is on AWS, it keeps improving Cloud providers are investing a lot in serverless
- 76. ACTIVELY IMPROVINGACTIVELY IMPROVING We're just at the beginning 30 seconds 👉 5 mins 👉 15 mins Node v6 👉 Node v8 👉 any version Faster VPN cold starts Websockets, SQS, ALB support Cloud providers are investing a lot in serverless Since most infra is on AWS, it keeps improving
- 77. ISIS SERVERLESSSERVERLESS THE FUTURE?THE FUTURE?
- 78. ISIS SERVERLESSSERVERLESS THE FUTURE?THE FUTURE? NO. IT'S THENO. IT'S THE PRESENTPRESENT..
- 79. TAL BEREZNITSKEYTAL BEREZNITSKEY Works: Co-Founder and CTO at Codes: Tweets: Writes: Torii github.com/berzniz @ketacode medium.com/ketacode ketacode.com berzniz.com