Module Map

DSM is organized as a multi-module toolkit so teams can pull in only the layers they need.

This page explains module boundaries. If you are integrating DSM into a service, start with the guides and Reference section first.

Module	Purpose
dsm-core	Runtime facade, collection contracts, diagnostics, observability SPI, lease and CRDT primitives
dsm-sync	Runtime control-plane and data-plane replication services
dsm-cluster	Transport-level cluster membership implementations
dsm-security	Message signing, replay protection, and cluster admission validation
dsm-spring-boot-autoconfigure	Runtime-first Spring Boot autoconfiguration
dsm-spring-boot-starter	Starter dependency for standard Boot integration
dsm-examples	Runnable reference examples
dsm-test-support	Fakes and reusable test transports
dsm-integration-test	End-to-end integration coverage

Layered View

application code
	|
	v
dsm-core
	|
	+--> collection contracts
	+--> runtime facade
	+--> diagnostics / observability SPI
	|
	+--> used by dsm-spring-boot-* modules
	+--> used by dsm-sync
			|
			+--> replication flows
			+--> repair flows
	|
	+--> paired with dsm-cluster for membership
	+--> paired with dsm-security for secure transport validation

Recommended Reading Path

Read dsm-core first. That is where the runtime API surface and collection builders live.

From there:

• read dsm-sync if you need to understand replication internals
• read dsm-cluster to choose membership behavior
• read dsm-security before planning production rollout
• read the Spring modules only if your service uses Boot

Integration Reading Path

first integration?
	|
	+--> Getting Started
	+--> Standalone Quickstart or Spring Boot
	+--> Runtime API / Collection Specs / Collection Handles
	+--> scenario cookbooks
	+--> architecture internals only when needed