One Year After Switching from Java to Go: Our Experiences

Re:One Year After Switching from Java to Go: Our Experiences by rahen on Wednesday February 19, 2025 @04:05AM (#43100131)

Cold latency is an issue with microservices. If you need to use Java, you'll likely end up using frameworks like Spring or Quarkus, which somewhat diminish the advantages of using the JVM and Java as a language.

At that point, you might as well start with Go from the beginning.

[ Parent | on HN ]

Re:One Year After Switching from Java to Go: Our Experiences by gf000 on Wednesday February 19, 2025 @06:10AM (#43100860)

Is it really an actual issue? How often do you restart instances or scale up horizontally?

A cheap 10 years old desktop PC can easily handle all the traffic a medium-sized website generates at all times.

[ Parent | on HN ]

Re:One Year After Switching from Java to Go: Our Experiences by pylua on Wednesday February 19, 2025 @07:48AM (#43101501)

What do you define as medium size?

[ Parent | on HN ]

Re:One Year After Switching from Java to Go: Our Experiences by gf000 on Wednesday February 19, 2025 @07:55AM (#43101587)

Stackoverflow famously ran on a single, although quite beefy server PC for a long time (not any longer, but not for performance reasons AFAIK).

I think it's a good data point to have to scale your workload to stackoverflow's, and reconsider the hardware costs.

(Obviously horizontal scaling has its place, but if it's that variably scalable, maybe there are better solutions, e.g. a single bigger instance -- often times even for cheaper)

[ Parent | on HN ]