How jasperfx/wolverine works
Principal modules
• Core Wolverine Library – This is the heart of the system; it contains the mediator, message bus, pipeline orchestration, dynamic handler discovery, error handling (e.g. circuit breakers, retries, fallbacks), middleware configuration, and logging.
• Transports Layer – Multiple directories (e.g. Transports/AWS, Transports/Azure, Transports/RabbitMQ, Transports/Kafka, Transports/MQTT, Transports/Pulsar, etc.) indicate that Wolverine supports many messaging protocols and external integration endpoints. Each transport module encapsulates sender/receiver logic, endpoint configuration, and adapter patterns.
• Persistence and Durability – A large set of folders in “src/Persistence” (including modules for Marten, Postgresql, RavenDb, SqlServer, RDBMS, etc.) shows that Wolverine offers various durable message storage implementations, outbox/inbox patterns, sagas, and durability agents for reliable message processing.
• Code Generation and Configuration – Directories under “build” and “src/Wolverine/Codegen” denote that part of the system dynamically generates handler chains and optimized serialization routines.
• Testing, Samples, and Documentation – There are many “Tests” and “Samples” directories for integration tests, benchmarks, and sample applications (e.g. CQRSWithMarten, KitchenSink, etc.) along with a full documentation site in “docs”.
– Message Mediation Core: Routes incoming messages to the correct handlers through a configurable middleware pipeline. Include details like dynamic handler discovery, error-handling policies, and continuation logic.
– Messaging Endpoints: Represent how messages enter/exit the system (HTTP endpoints, local queues, etc.).
– Pipeline & Middleware: A sub-component handling retries, circuit breakers, side effects, auditing, and logging.
• Optionally, include an “API / Integration” container for sample apps and administrative endpoints (for example, the HTTP demonstration projects and Admin APIs shown under src/Http and other sample projects).
• “Developer Tools & Build” – the use of Bullseye for the build pipeline, automated tests via GitHub workflows, Docker Compose for test integration, and code snippet generation for documentation.