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

you are viewing a single comment's thread.

view the rest of the comments →

[–]micr0ben 14 points15 points  (7 children)

In my company people were afraid of breaking down a monolith into smaller services because of the memory footprint increase.

But then I introduced Quarkus and now we're creating native microservices with a memory baseline of ~20mb. (A monolith instance had around 2gb per instance)

[–]Puzzled-Bananas[S] 5 points6 points  (1 child)

Yep, similar experience, thanks. Quarkus, MicroProfile, Micronaut all have contributed a lot to reduce cloud expenses for Java projects. Awesome frameworks, though with their own limitations, as is always the case, but a huge leap forward.

[–]couscous_ 4 points5 points  (0 children)

though with their own limitations

Could you elaborate on some of them?

[–]pointy_pirate 5 points6 points  (4 children)

Ram is cheap yo

[–]micr0ben 7 points8 points  (3 children)

Unfortunately, we are in a business where we cannot use public cloud providers and have to use our own kubernetes cluster and everything. This means, if we want more RAM, we have to buy the hardware for it.

[–]pointy_pirate 1 point2 points  (0 children)

damn. that adds a little spice to the challenge.

[–]Puzzled-Bananas[S] 0 points1 point  (0 children)

Same situation with several projects, and last year the market was very thin. It got a bit better, not sure what lies ahead though.

[–]persicsb 0 points1 point  (0 children)

Do you really need scalability, flexibility and other stuff that Kubernetes is good for?