Spring Middleware documentation is organized as a set of platform guides for Spring Boot microservices. Start with the architecture and service discovery model, then explore communication, GraphQL federation, messaging, security, logging, Redis, caching, and data integrations depending on your use case.
Spring Middleware is not a single feature. It is a platform layer with multiple capabilities. The documentation is therefore split into platform guides and focused capability pages.
Some pages describe reusable runtime capabilities such as Kafka, RabbitMQ, or GraphQL federation. Others explain platform-wide concerns such as topology, registry metadata, errors, logging, and declarative communication.
These pages give the best entry point into the platform if you are new to Spring Middleware.
These guides describe cross-service concerns and the shared behavior that defines the platform model.
Registry-driven architecture, control plane, service topology, convergence, and runtime flow.
How the platform is split into reusable module groups and how services adopt them incrementally.
Topology metadata, schema locations, service registration, and the control-plane model.
Declarative clients, service resolution, request propagation, and remote execution behavior.
Unified error model, propagation across services, and consistent failure representation.
Request and response logging, correlation identifiers, and platform-level observability behavior.
These pages explain how specific platform capabilities work once a service is on the platform.
Schema registration, composition, GraphQL Links, gateway execution, and distributed schema behavior.
Platform-wide messaging overview covering Kafka and RabbitMQ as complementary messaging models.
Publishers, subscribers, topic configuration, event envelopes, retries, and dead-letter behavior.
JMS-like resources, handlers, listeners, error handlers, acknowledgement, and lifecycle control.
These guides cover reusable integrations that services can adopt as part of the platform layer.
Dynamic search capabilities and reusable query composition for MongoDB-backed services.
Dynamic search infrastructure and reusable patterns for relational persistence.
Distributed maps, locks, shared state, and Redis-backed platform utilities.
Redis-based caching with TTL configuration, runtime statistics, cache inspection, and programmatic cache management.
These topics define how services stay protected and observable while participating in the platform.
Explore the related guides and capability pages to understand how this part of Spring Middleware fits into the broader runtime model.