I am very concerned too, we rely on Spring and RabbitMQ heavily. I’m going to call a halt on Spring and Rabbit for all new projects until the M&A fog dissipates. We run our own tech radar, likely to set the entire VMware stack on hold for now. If any of the prolific Spring contributors leaves, we’ll consider moving altogether. Spring is such a complex framework, if Broadcom gets to reshuffle the team, pieces will start to crumble.

One might argue that if "Spring is such a complex framework" you never should have been using it in the first place?

The framework is complex, not its use. It’s actually extremely easy to use. If a project builds a framework that tries to cover every case in an opinionated way, they’re going to end up with a complex framework. Why should the fact that the framework externalises most complexities mean that it shouldn’t be used?

I am also concerned about this. VMWare have been great stewards of the Spring framework / boot libraries.

I would like to know as well. I am worried about RabbitMQ.