←back to thread

210 points mmoogle | 3 comments | | HN request time: 0s | source
Show context
ntqz ◴[] No.44608949[source]
I could see the writing on the wall with this.

On that note, I'm already looking at migrating my codebase off of Spring. Just testing the waters with Quarkus, Helidon, Micronaut, Pekko, Vert.x, and plain Jakarta EE right now.

replies(3): >>44609703 #>>44610521 #>>44611297 #
_1tan ◴[] No.44609703[source]
Are there any indications or just a feel?
replies(1): >>44609844 #
bags43 ◴[] No.44609844[source]
Company where I work had huge risk audit.

The second highest risk is using USA based cloud with 66/100.

The first one was using Spring Boot everywhere 77/100. Till the end of 2025 we need to have migration path to something else with 2 PoCs done.

replies(4): >>44609971 #>>44610952 #>>44611105 #>>44611548 #
1. jcrben ◴[] No.44610952[source]
What was the actual risk of using SpringBoot tho?
replies(1): >>44611817 #
2. ntqz ◴[] No.44611817[source]
License changes - BSL or closing the source

If there's no money in it for them - reduction of staff or funding leading to slower releases and bugfixes

Moving some features like Spring Cloud / Spring Integration, or new development behind a paywall (think RHEL)

Big users (like Netflix, Walmart, JPMorgan, LinkedIn/Microsoft, etc) would likely be able to pay for it (until they moved off), but smaller companies and individual developers not so much

replies(1): >>44614069 #
3. bbkane ◴[] No.44614069[source]
I think it would be more of a Redis situation - steward changes the license, someone large enough to maintain a fork creates one, and everyone moves to the fork. In Redis's case, Amazon forked it into Valkey.

Spring is so widely used that there are multiple "large enough" companies who could do this