Which is a bit similar with SQL or NoSQL.
> Different services have different data storage requirements. For some services, a relational database is the best choice. Other
> services might need a NoSQL database such as MongoDB, which is good at storing complex, unstructured data, or Neo4J,
> which is designed to efficiently store and query graph data.
The patterns of either a DB per service or a shared (multi-tenant) DB are hardly something for an extra framework, especially not at MicroProfile or Spring IMO. Something like Liquibase may help with that.
Other patterns like CQRS or Event Sourcing were discussed but I don't think those discussions resulted even in a sandbox proposal so far.
Jakarta NoSQL also got inspired by those, so if may well be better suited for a "Persistence light" or "Persistence Commons" as Arjan hinted in the JNoSQL mailing list for synergies and common elements between JPA and Jakarta NoSQL.
The way both Spring Data and Micronaut allow to integrate it with the DI or CDI spec, it could also complement Jakarta EE standards the way they already do.
There was an interesting session about popular Microframeworks today at JCON (where Rudy also is;-) in the last slot. It mentioned Micronaut or Spring Boot having these types of data access libraries, while others require to write repositories by hand if you want to use that pattern.