When Spring Boot 2.0 was released, there were a lot of breaking changes that millions of users had to deal with. How they handled the deprecation and removal of legacy features was to bundle the removal with many other benefits of migration. I saw this with Neo4j as well. Another example today of a big OSS change would be the removal of Zookeeper from Apache Kafka. We should look at that as a kind of case study on operational costs of these kinds of decisions.

IMHO, we should always thrive for marching towards a cleaner/better/scalable architecture, while providing easy migration paths to existing deployments. Both are equally important, sacrificing one over the other would not be ideal. And one's point of view can change very quickly based on which side of the fence they are on 🙂

Totally. Great point @Mayank. This is why it is so important to be in-tune with community users from all backgrounds. We can’t understand the pain if we aren’t having those conversations.

👍