How spring-projects/spring-session works
Project type and purpose
• This is an open-source, multi-module Java library (“Spring Session”) that provides a core session-management API plus multiple storage‐adapter modules (Redis, JDBC, Hazelcast, MongoDB), documentation, samples, and build infrastructure.
• Its primary function at runtime is to replace or augment the container’s HttpSession/WebSocket/WebSession support in a container-neutral way.
File structure
• Top-level files: settings.gradle, build.gradle, gradle.properties, CI workflows under .github, release scripts under scripts/release.
• buildSrc/: custom Gradle plugins and conventions applied to all modules.
• Modules (each under its own directory):
• spring-session-core (defines SessionRepository API, filters, runtime hints)
• spring-session-data-redis
• spring-session-jdbc
• spring-session-hazelcast
• spring-session-data-mongodb
• spring-session-bom & spring-session-dependencies (dependency management)
• spring-session-docs (Antora-based documentation site)
• spring-session-samples (dozens of sample Spring Boot and JavaConfig applications)
• etc/: style and IDE configuration; etc/checkstyle; gradle/wrapper; scripts/release.
README for additional insights
• Confirms core vs. data modules.
• Lists supported transports (HttpSession, WebSocket, WebSession).
• Notes Gradle-based build and sample locations.
Diagramming conventions
• Use clear, consistent labels for each module or component.
– Blue rectangles for core modules
– Green for adapters
– Orange for samples
– Gray for build/CI infrastructure
Be very detailed—break out filters, interfaces, adapters, stores, build plugins, CI workflows, docs, and samples as separate components to fully capture the architecture.