Persistence Wars: become the Jedi of distributed Java architectures, Otavio Santana

A long time ago in a galaxy far, far away…, it became relatively straightforward to design and implement our application's data persistence solution. Nowadays we live in a world where modern cloud-native and distributed solutions adoption increases yearly critical for us to know how the impacts of such changes on our data integration layer - after all, it is often tagged as a performance bottleneck. Not only a bottleneck, but a small mistake in this layer might also impact the whole architecture and it is really expensive to change it later. In this talk, we'll cover, in a Java context, topics such as transactionality concerns, impacts of poorly designed persistence layers, patterns and best practices, polyglot architectures and the adoption of different paradigms such as NoSQL, the framework's hidden traps you may fall into in exchange for development speed, the evolution of the JakartaEE platform in the face of new development needs, how to handle data throughout application modernization processes and much more. Don't miss out on this architecture-driven journey that will enable you to design and deliver modern distributed Java solutions that rely on a powerful, long-lasting, reliable persistence layer.

[KarthikKumar-bd]

When we use Pageable, and use findall()... does it load all the data from db and keep it memory or does it query specified amount of data from db as we query?