One Year After Switching from Java to Go: Our Experiences

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

Spring Boot startup time is indeed a problem, especially when scaling horizontally on low cpu nodes.

If your environment allows for burst cpu usage until ready to accept traffic, you can start up really fast as spring does so much reflection magic during startup that can't be done during compilation "trivially". You can include hints for runtime configuration from a build, but it doesn't do much to help in really low cpu envs.

Then you can of course just do native images, but you lose some of the spring "magic", and might be annoying to refactor towards.

[ Parent | on HN ]

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

I’ll have to look into burst cpu usage. Thanks

[ Parent | on HN ]

Re:One Year After Switching from Java to Go: Our Experiences by ivan_gammel on Thursday February 20, 2025 @06:16AM (#43113413)

This actually makes me wonder if it is possible to preserve post-startup state and then restore it as a way to mitigate long computational stage during startup. I bet it is, maybe we could just serialize the application context and restore it.

[ Parent | on HN ]