Most active commenters

    ←back to thread

    Broadcom to discontinue free Bitnami Helm charts

    (github.com)
    209 points mmoogle | 23 comments | 18 Jul 25 19:29 UTC | HN request time: 0.894s | source | bottom
    1. ntqz ◴[18 Jul 25 19:39 UTC] 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 #
    2. _1tan ◴[18 Jul 25 20:52 UTC] No.44609703[source]▶
    Are there any indications or just a feel?
    replies(1): >>44609844 #
    3. bags43 ◴[18 Jul 25 21:07 UTC] 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 #
    4. jchmbrln ◴[18 Jul 25 21:21 UTC] No.44609971{3}[source]▶
    I’m completely out of the loop. What’s going on with Spring Boot?
    replies(2): >>44610003 #>>44610074 #
    5. radicalbyte ◴[18 Jul 25 21:24 UTC] No.44610003{4}[source]▶
    The VMware apocalypse.
    replies(1): >>44610028 #
    6. heisenbit ◴[18 Jul 25 21:27 UTC] No.44610028{5}[source]▶
    One does not need VMware for SpringBoot so?
    replies(3): >>44610087 #>>44610088 #>>44610090 #
    7. xienze ◴[18 Jul 25 21:33 UTC] No.44610074{4}[source]▶
    Probably a bit of overreaction given that Broadcom is now in charge of Spring. At the end of the day it’s a wildly popular open source project — it has a path forward if Broadcom pulls shenanigans.

    That said, I have noticed that the free support window for any given version is super short these days. I.e. if you’re not on top of constantly upgrading you’re looking at paid support if you want security patches.

    8. xienze ◴[18 Jul 25 21:34 UTC] No.44610087{6}[source]▶
    Spring’s corporate steward is VMWare, and Broadcom bought VMWare, ergo Spring is subject to Broadcom’s whims.
    9. TYMorningCoffee ◴[18 Jul 25 21:35 UTC] No.44610088{6}[source]▶
    VMware owns Spring Boot https://en.m.wikipedia.org/wiki/Spring_Boot
    10. loloquwowndueo ◴[18 Jul 25 21:35 UTC] No.44610090{6}[source]▶
    Not spring boot, but spring, is owned by VMware. Sure spring is under a free license but if upstream enshittifies, community forks would be required.
    replies(2): >>44611037 #>>44614624 #
    11. lapusta ◴[18 Jul 25 22:34 UTC] No.44610521[source]▶
    Red Hat effectively killed their JBoss/Middleware team and the rest of it moved to IBM https://www.redhat.com/en/blog/evolving-our-middleware-strat... Quarkus and other tools were pushed to CommonHaus/Apache. I believe Vert.X was also mostly developer by RH team, although moved to Eclispe Foundation a decade ago.

    Oracle also ended up somehow sponsoring 2 frameworks: Helidon & Micronaut.

    I'd bet Spring is still the safest choice next to Jakarta EE standards that all are built on top of nowadays.

    replies(2): >>44611133 #>>44611305 #
    12. jcrben ◴[18 Jul 25 23:26 UTC] No.44610952{3}[source]▶
    What was the actual risk of using SpringBoot tho?
    replies(1): >>44611817 #
    13. mindcrime ◴[18 Jul 25 23:36 UTC] No.44611037{7}[source]▶
    And as popular and widely used as Spring is, that would 100% happen. To me at least, I wouldn't count this as a particularly huge risk. But in an enterprise setting, with mandatory auditing and stuff, I can understand why there would be a requirement to at least pre-identify alternative(s).
    14. ◴[18 Jul 25 23:46 UTC] No.44611105{3}[source]▶
    15. latchkey ◴[18 Jul 25 23:50 UTC] No.44611133[source]▶
    I still see Gavin working on JEE.
    16. EdwardDiego ◴[19 Jul 25 00:17 UTC] No.44611297[source]▶
    I quite like Micronaut, especially the ability to use its compile time DI as a standalone library in a non-Micronaut app.

    Quarkus is pretty similar, but is built on top of Vert.x so a lot of the fun of Vert.x (don't block the event loop!) is still present. It also does compile time DI.

    17. EdwardDiego ◴[19 Jul 25 00:18 UTC] No.44611305[source]▶
    Yeah my old colleagues who work on Kroxylicious are now IBM. I keep asking them if they're wearing a blue tie to the office yet, they still don't think it's funny.
    18. somehnguy ◴[19 Jul 25 00:58 UTC] No.44611548{3}[source]▶
    What's the actual risk though? Just saying it's the riskiest at 77/100 doesn't mean anything.
    replies(1): >>44615352 #
    19. ntqz ◴[19 Jul 25 01:48 UTC] No.44611817{4}[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 #
    20. bbkane ◴[19 Jul 25 09:58 UTC] No.44614069{5}[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

    21. terminalbraid ◴[19 Jul 25 11:35 UTC] No.44614624{7}[source]▶
    > Not spring boot, but spring, is owned by VMware

    How do I reconcile this statement with VMWare holding the copyright which you will find unambiguously littered in the official Spring Boot repository?

    Since you contend the contrary, who does in fact hold the copyright?

    replies(1): >>44615159 #
    22. ◴[19 Jul 25 13:03 UTC] No.44615159{8}[source]▶
    23. bags43 ◴[19 Jul 25 13:34 UTC] No.44615352{4}[source]▶
    Among others:

    - license change -> restricting features behind a paid tier (https://spring.io/blog/2025/04/21/spring-cloud-data-flow-com...)

    - reducing headcount of people -> slow security patching + not following industry standards

    - all eggs in one basket :)

    - cut from major clouds (Azure Spring apps)