Good preso. A lot of ground w/o a lot of AWS boilerplate. Gets to the point. Thanks. Would like more info on scale up/down thresholds/triggers and settablity for cpu, network, and memory. "If ANY cross threshold (up), we scale UP." and "If ALL cross threshold (down), we scale DOWN" but if SOME stay up ...and the rest go down ... then we stay UP at peak provisioning? concerned about a chance of getting 'stuck' on high, there....
Hehe, throughout the talk, I don't think the provided subtitles ever actually showed the word "serverless" :P I expect Amazon created these automatically, but it's still weird that Amazon software doesn't understand the word serverless 🤭
Impressive presentation and technology!
Thanks for your positive feedback!😍
it will be great to have scheduled scale
Good preso. A lot of ground w/o a lot of AWS boilerplate. Gets to the point. Thanks.
Would like more info on scale up/down thresholds/triggers and settablity for cpu, network, and memory.
"If ANY cross threshold (up), we scale UP."
and
"If ALL cross threshold (down), we scale DOWN"
but
if SOME stay up ...and the rest go down ... then we stay UP at peak provisioning?
concerned about a chance of getting 'stuck' on high, there....
I think it makes perfect sense, it should scale in regard to maximum cpu, memory or network required!
Im impressed!!
Why would one of those be higher disproportionate to another? They would proportionately be raised!
This is dope!
Hehe, throughout the talk, I don't think the provided subtitles ever actually showed the word "serverless" :P I expect Amazon created these automatically, but it's still weird that Amazon software doesn't understand the word serverless 🤭
The subtitles have been horrible.
Sorry to hear about this. I've passed it along to our team for a closer look. 🔎 Thank you. ^AD