Welcome to the Quantum Space Organization on GitHub! This organization hosts a collection of .NET libraries and frameworks designed to help you build robust, scalable, and maintainable applications.

Here's a list of the packages currently available:

• Quantum.Branch: Improves branching logic. (Support scenarios for multi-copany or multi-branching)
• Quantum.Core: Provides fundamental building blocks for other Quantum packages.
• Quantum.DataFlow: Facilitates data processing pipelines.
• Quantum.Dispatcher: Improves command dispatching.
• Quantum.Domain: Provides base classes and utilities for Domain-Driven Design.
• Quantum.ProductInfo: Manages product information.
• Quantum.Specification: Implements the Specification pattern.

• Quantum.Configurator: Handles application configuration.
• Quantum.ConfigurationManagement: Handles complex configuration scenarios.

• Quantum.CorrelationId: Generates and propagates correlation IDs for distributed tracing.
• Quantum.InboxOutbox: Provides implementations for the Inbox/Outbox pattern.
• Quantum.InboxOutbox.Configuration: Configuration settings for Inbox/Outbox.
• Quantum.InboxOutbox.Inbox: Implementation of the Inbox.
• Quantum.InboxOutbox.Outbox: Implementation of the Outbox.
• Quantum.ServiceBus: Abstractions for working with message buses.
• Quantum.ServiceBus.InMemory: In-memory implementation of the Service Bus.
• Quantum.ServiceBus.RabbitMQ: RabbitMQ implementation of the Service Bus.
• Quantum.Sequencer: Handles sequential processing of operations.
• Quantum.TimeSequencer: Handles time-based sequential processing.

• Quantum.DataBase: Provides base classes and utilities for database interactions.
• Quantum.Epoch: Handles epoch-based operations.
• Quantum.EventSourcing: Infrastructure for building event-sourced systems.
• Quantum.EventSourcing.Enrichers: Tools for enriching events.
• Quantum.EventSourcing.EventStoreDB: Integration with EventStoreDB.
• Quantum.EventSourcing.InMemoryEventStore: In-memory implementation of an event store (for testing).
• Quantum.EventSourcing.SqlServerProjector: SQL Server projector for event sourcing.
• Quantum.EventSourcing.Test: Utilities for testing event-sourced systems.
• Quantum.EventSourcing.Versioning: Support for event versioning.
• Quantum.Snowflake: Implements the Snowflake ID generation algorithm.

• Quantum.Resolver: Abstractions for dependency resolution.
• Quantum.Resolver.Autofac: Integration with the Autofac DI container.
• Quantum.Resolver.ServiceCollection: Integration with the Microsoft.Extensions.DependencyInjection.

• Quantum.I18n: Provides internationalization (i18n) support.

• Quantum.Logging: Abstractions for logging.
• Quantum.Logging.SqlServer: SQL Server logging provider.
• Quantum.OpenTelemetry: Integration with OpenTelemetry.
• Quantum.Telemetry.HealthCheck: Provides health check endpoints.

• Quantum.ExceptionHandler: Provides exception handling mechanisms.
• Quantum.MonkeyPatch://TODO
• Quantum.MultiTenant: Support for multi-tenant applications.
• Quantum.PolicyProvider: Provides policy management capabilities.
• Quantum.ReportingTemplate: Provides a base template for reporting
• Quantum.ServiceDiscovery: Abstractions for service discovery.
• Quantum.ServiceDiscovery.Consul: Consul implementation for Service Discovery
• Quantum.ServiceDiscovery.Extensions: Extensions for Service Discovery
• Quantum.ServiceDiscovery.SqlServer: SQL Server implementation for Service Discovery
• Quantum.ServiceDiscovery.Tests: Test utilities for Service Discovery
• Quantum.Services: //TODO

To get started with any of these packages, you can install them via NuGet. For example, to install Quantum.Configurator, you would use the following command in the NuGet Package Manager Console:

Install-Package Quantum.Configurator

We welcome contributions to the Quantum Space project! If you'd like to contribute, please read our Contributing Guidelines.

A big thank you to our contributors and maintainers who keep this project going!

Your support helps us maintain and improve these libraries. Consider donating to our Open Collective: Or, you can also support us through GitHub Sponsors.

Please follow the code style used in the project.

Please use clear and concise commit messages. A good commit message should include:

• A brief summary of the changes (in the first line).
• A more detailed description of the changes (in the body).
• A reference to the issue that the changes address (if applicable).

Example:

Fix: Bug in data processing

This commit fixes a bug in the data processing module that caused incorrect results.
The bug was caused by an incorrect calculation in the process_data function.
This commit also adds a new test case to ensure that the bug is fixed.

Closes #12