A cup of coffee and a good talk about tech, productivity, travel and programming. A bit of my day-to-day, Ruby on Rails, Javascript, React, frameworks and other hyped technologies
A cup of coffee and a good talk about tech, productivity, travel and programming. A bit of my day-to-day, Ruby on Rails, Javascript, React, frameworks and other hyped technologies
Yeah. It's a pain! We don't have any customers yet, but we're paying thousands just to set up the Lambda infrastructure, which I think is not the best way to go about things, but its not my choice. Ideally we should write a single stateless server that is always on, and when we need to scale then we can figure how to deploy to Lambdas. At the moment, we're completely coupled to Lambdas and we can't run our services outside of Lambdas, which make development a pain.
EU ๐ช๐บ | Art, Tech & Good Vibrations ๐คณ | Founder of แดแดแดแดสสแดแดก ๐ hellotomorrow.agency โข Just started working on a new endeavour ๐ usepoe.app โข Follow me on Twitter!
Location
Brussels, Belgium
Work
UX Engineer, Product Manager, sometimes Designer at Self
A cup of coffee and a good talk about tech, productivity, travel and programming. A bit of my day-to-day, Ruby on Rails, Javascript, React, frameworks and other hyped technologies
A cup of coffee and a good talk about tech, productivity, travel and programming. A bit of my day-to-day, Ruby on Rails, Javascript, React, frameworks and other hyped technologies
A cup of coffee and a good talk about tech, productivity, travel and programming. A bit of my day-to-day, Ruby on Rails, Javascript, React, frameworks and other hyped technologies
Cold start can be an issue.
We have the same issues with AWS lambdas where I work. Sometimes 30 seconds just to "warm up". It's retarded!
Besides that, configuring lambdas was a pain, at least to me.
Yeah. It's a pain! We don't have any customers yet, but we're paying thousands just to set up the Lambda infrastructure, which I think is not the best way to go about things, but its not my choice. Ideally we should write a single stateless server that is always on, and when we need to scale then we can figure how to deploy to Lambdas. At the moment, we're completely coupled to Lambdas and we can't run our services outside of Lambdas, which make development a pain.
How much of an issue? Like milliseconds, seconds...?
Some seconds. I had some functions that took something between 4 and 5 seconds on cold start.
Shouldn't you break apart such functions?
It sounds like you're trying to do too much in a function.
What technology stack are you running?
Iโm running node. My functions are very small, doing a tiny service
I'm sure you know this, but sometimes you can run a script that continuously invokes it.
That helps but doesn't necessarily keep all the containers running, it typically depends on the scale and volume.
I know that, but it doesn't seem to be a good practice
That kinda defeats the point of only running it when needed.
You run it every 30 minutes, just as the underlying container is about to close. You don't invoke it constantly.