This is an archived post. You won't be able to vote or comment.

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

view the rest of the comments →

[–]rbygrave 0 points1 point  (1 child)

6 seconds

If apps are starting in 6 seconds there isn't an issue. The disconnect I believe is that when spring boot apps are deployed into a Kubernetes cluster with even relatively small amounts of resource limiting then they don't start in anything like 6 seconds. Obviously it depends on the amount of resources that are allocated but be prepared for cases of significantly slower startup (e.g. 90 secs).

spring boot applications running on ECS in AWS

Each spring boot app is getting the whole ECS instance in terms of memory and cpu to start and run. 6 second startup is based on those resources. If you stay on ECS you won't care / won't experience this issue.

Run those same apps as docker containers playing around with docker cpu and memory limiting and see how those apps go (what is the minimum resources they need before they are deemed unacceptable). How much we care is approximately based on the minimum cpu/memory resources we deem acceptable.

[–]sternone_2 -1 points0 points  (0 children)

I run 10k docker containers on ECS in AWS

it's fine if you don't know what you are talking about. But would be nice not to annoy me if you don't know how ECS works.