codeconsole commented on PR #15745: URL: https://github.com/apache/grails-core/pull/15745#issuecomment-4759049684
This is for apps that already have or need both, where today the only option is two separate `MongoClient`s with no transactional consistency between them. The module makes that coexistence correct: GORM and Spring Data share one `MongoClient`, database and codec registry, and — within a single `@Transactional` — the same MongoDB `ClientSession`, so a GORM `save()` and a `MongoTemplate`/repository write commit or roll back together. Concrete cases: Spring-ecosystem libraries built on `MongoTemplate`/Spring Data repositories (Spring Batch, Spring Session, Spring Integration, Spring Security ACL); incremental migration in either direction without doubling connections; and reaching actively-developed Spring Data features for specific operations while keeping GORM for domain modeling. It's opt-in — a separate module that pulls in `spring-data-mongodb` only when an app adds it; core stays driver-only and the mapping models stay separate. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
