What is "Serverless"?

on YouTube ↗31m

" summary

Panel defines serverless as small, event-triggered code — essentially function as a service — best for API gateways, simple translations, background jobs and parallel data processing, not for whole transactional apps that require ordering or strong atomicity. Operational issues include cold-start cost on JVMs, CI/CD and ownership of proliferating functions; one group cites a working example on AWS Lambda + DynamoDB. Expect modest latency and eventual-consistency tradeoffs, tooling gaps for dependency mapping, and adoption timelines measured in years rather than weeks.

AI-written summary · about

" chapters (11)

1. 0:00Introduction to panel
2. 1:03Defining serverless computing
3. 3:31Good use cases for serverless
4. 8:28Bad fits for serverless
5. 13:22Organizational impact of serverless
6. 21:26Audience experiences with serverless
7. 23:49Kernels and serverless fit
8. 25:45Microservice size debate
9. 27:51Resource utilization efficiency
10. 28:41Spring Cloud Data Flow role
11. 30:37Closing and Q&A

" related talks

• 06mAn introduction to serverlessMike Roberts · O'Reilly Software Architecture Conference 2017 - New York, New York
• 28mServerless - the way microservices should beIvan Jovanovic · OdessaJS 2018
• 35mServerless Experiences -- On Your Own Servers?Evan Anderson · Serverless Practitioners Summit 2019
• 42mNo Server Is Better Than No Server: Building Blocks for Serverless ArchitecturesConstantin Gonzalez · code.talks 2017
• 04mServerless, Revealed!Daniel phrawzty Maher · dotScale 2018
• 58mServerless - the brief past, the bewildering present, and the beautiful (?) futureMike Roberts · NDC London 2018
• 48mThe future will be ServerlessLuciano Mammino · jsDay 2018
• 52mConfusion In The Land Of The ServerlessSam Newman · NDC Sydney 2017