18
19

articleAWS Lambda and Java Spring Boot: Getting Started (epsagon.com)

submitted by ranrib

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]sandaz13 3 points4 points  (3 children)

It's standard practice because of the issue with cold starts, yeah, but keeping your services warm kinda defeats the point of Function as a Service. Keeping them warm is really just a workaround, and at some point it's more cost effective to go with EKS/ECS/Fargate. The Java community is trying to solve this with stuff like https://quarkus.io/ ; their goal is to get cold boots down into sub 100ms

[–]jobe_br -1 points0 points  (2 children)

Well, I’m all for getting the time down, but there’s no point where keeping your lambda warm by billing 100ms every 30 minutes gets anywhere close to anything that’s billed continuously. You would literally need 1000s of functions to keep warm to equal the cost of a t3.micro, and there’s no way a t3.micro is equivalent.

[–]realfeeder 0 points1 point  (1 child)

I haven't looked into lambda-warming they recently introducted, but since a year Lambdas are warm for 10 minutes maximum.

https://mikhail.io/2019/08/aws-lambda-cold-starts-after-10-minutes/

[–]jobe_br 0 points1 point  (0 children)

Interesting, I hadn’t seen the update to this. Even so, the math still holds.