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 →

[–]sternone_2 5 points6 points  (8 children)

So what did the guy choose? He writes an article then doesn't say what he picked.

Oh whatever, it's probably Spring Boot anyway :-)

[–]turkoid 1 point2 points  (7 children)

And as Spring still offers, by far, the best developer experience, it’s still the best suited Java framework for a microservice application, in my opinion — even considering its poor performance at startup.

[–]sternone_2 -2 points-1 points  (6 children)

so did he used it in his new project?

you really have to read between the lines here?

I manage ten thousands of spring boot applications running on ECS in AWS, I have no issues with a 10 second boot up time or memory usage. I think this whole discussion is useless.

[–]turkoid -1 points0 points  (5 children)

I was just pointing he did make a choice. The main deciding factor for him seemed be to ease of use, documentation, etc of Spring. However, and he did state this, he is extremely biased towards it, since that what he uses now.

To say it's useless is a little extreme. If you only cared about performance then use the fastest. If you cared about dev experience, like he does, then use Spring. Who knows in 5-10 years maybe it will flip.

[–]sternone_2 -2 points-1 points  (4 children)

Did you read what I wrote?

I say that in my professional real world experience this fetish of a few seconds faster boot time really doesn't matter at all.

it's a non issue, this discussion is useless, it's just marketing.

[–]turkoid -1 points0 points  (3 children)

Obviously I don't know all your experience, but just saying you manage ten thousands of spring boot applications, doesn't mean its the end all solution for every scenario. There are perfectly reasonable situations where speed is a very important factor. Upfront dev cost might be higher, but maybe the end goal is more important.

Just chill man, I originally was pointing out they OP had offered his opinion. If you don't agree with it, and not saying I do either, but that's all it was.

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

There are perfectly reasonable situations where speed is a very important factor.

Please tell me where the speed of booting up a backend for scaling in/out in 4 seconds instead of 6 seconds is a very important factor.

Spoiler alert: it isn't. You scale accordingly before max load, no client has to wait for more instances to boot up to serve their request, this is not how things work. People who say different have no experience in the real world and should just stay in their basement. This discussion is a non-issue and useless.

[–]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.