As infinispan has a complex impl to make it work, requiring all the Lucene indexing to extract data and make it searchable and also it doesn’t work with Kafka or have eventual consistency with debezium, I’m happy to +1 its removal.
Mark On Tue, 1 Apr 2025 at 12:23, Alex Porcelli <porce...@apache.org> wrote: > As part of the ongoing effort to upgrade to the latest Quarkus LTS version, > we’re currently dealing with the impact of aligning with Infinispan 15, > which introduces a new set of changes and potentially api compatibility > issues. > > Given this context, I’d like to revisit the question: Do we really want to > continue supporting Infinispan? > > This has been discussed in the past, and there was some resistance to > removing it. However, maintaining support goes beyond the existing > implementation—it requires us to stay on top of future upgrades, adapt to > API changes, and deal with potential security vulnerabilities stemming from > Infinispan itself and its transitive dependencies. > > I believe it’s worth re-evaluating its value and whether it’s aligned with > the future direction of the project. > > Looking forward to your thoughts. > > - > > Alex >
