Spring Session Modules
In Spring Session 1.x, all of the Spring Session’s SessionRepository implementations were available within the spring-session artifact.
While convenient, this approach was not sustainable long-term as more features and SessionRepository implementations were added to the project.
Starting with Spring Session 2.0, the project has been split into Spring Session Core module and several other modules that carry SessionRepository implementations and functionality related to the specific data store.
Users of Spring Data should find this arrangement familiar, with Spring Session Core module taking a role equivalent to Spring Data Commons and providing core functionalities and APIs, with other modules containing data store specific implementations.
As part of this split, the Spring Session Data MongoDB and Spring Session Data GemFire modules were moved to separate repositories.
Now the situation with project’s repositories/modules is as follows:
-
-
Hosts the Spring Session Core, Spring Session Data Redis, Spring Session JDBC, and Spring Session Hazelcast modules
-
-
spring-session-data-mongodbrepository-
Hosts the Spring Session Data MongoDB module. Spring Session Data MongoDB has its own user guide, which you can find at the [https://spring.io/projects/spring-session-data-mongodb#learnSpring site].
-
-
spring-session-data-geoderepository-
Hosts the Spring Session Data Geode modules. Spring Session Data Geode has its own user guide, which you can find at the [https://spring.io/projects/spring-session-data-geode#learn site].
-
Finally, Spring Session now also provides a Maven BOM (“bill of materials”) module in order to help users with version management concerns:
-
-
Hosts the Spring Session BOM module
-