27:50 You suggest that size of a Lambda function does not impact a cold start time. Interestingly enough AWS recommends to avoid big functions because they found that bigger functions have a slower cold start: th-cam.com/video/oQFORsso2go/w-d-xo.html
@David Schmitz (i hope you read it): Can you explain in more detail why you decided not to use the serverless framework? most of the stuff you described seems to be covered by it!?
Hey... well in general, I try to avoid invasive frameworks if I can and if it makes sense. E.g. I would not try to rebuild Express. Imho the serverless ecosystem is too young to commit to a single framework like claudia or serverless. Although I like both and both have matured....and truth to be told, with this architectural style you can introduce and mix frameworks rather easily.
Dave is wrong on this one. Kubernetes is the future. Standard apis, standard deployment, powerfull abstractions that work on AWS, Azure, GCP, everwhere. Serverless is vendor lock-in trash. Terraform is also a quasi declarative system (not really), terraform is stateful and is miles behind helm and the like
![AWS re:Invent 2019: [REPEAT 3] Serverless architectural patterns and best practices (ARC307-R3)](http://i.ytimg.com/vi/9IYpGTS7Jy0/mqdefault.jpg)
This is STILL a great presentation today. Anybody besides me watching in 2021?
Real production-ready arch! thanks a lot that's all I need to talk to the boss!
Thank you for sharing your insights and real world experiences
excellent talk
Amazing video on serverless so far
Nice presentation for beginners at serverless
27:50 You suggest that size of a Lambda function does not impact a cold start time. Interestingly enough AWS recommends to avoid big functions because they found that bigger functions have a slower cold start: th-cam.com/video/oQFORsso2go/w-d-xo.html
can you tell me more about your system's new architecture . which you shown at start
Great talk!
Cool dude! learned a lot.
Show this to people who think Germans have no sense of humor :)
@David Schmitz (i hope you read it): Can you explain in more detail why you decided not to use the serverless framework? most of the stuff you described seems to be covered by it!?
Hey... well in general, I try to avoid invasive frameworks if I can and if it makes sense. E.g. I would not try to rebuild Express. Imho the serverless ecosystem is too young to commit to a single framework like claudia or serverless. Although I like both and both have matured....and truth to be told, with this architectural style you can introduce and mix frameworks rather easily.
Thank you for the video :)
Dave is wrong on this one. Kubernetes is the future. Standard apis, standard deployment, powerfull abstractions that work on AWS, Azure, GCP, everwhere. Serverless is vendor lock-in trash. Terraform is also a quasi declarative system (not really), terraform is stateful and is miles behind helm and the like
Funny guy! :)
I cannot see anything ------ let me ask some questions lol