The platform’s Infrastructure pillar is a set of packages, each published to NuGet.org on its own, so an application references only what it uses, without adopting the rest of the platform:

dotnet add package Anarchy.Toolkit.Infrastructure.Messaging.Aws

Each package’s README (on NuGet.org and in the Package Catalog) explains when to use it and how to wire it up. The samples show complete applications.

Registering services

Each package with concrete services ships a dependency-injection entry point, either an IDependencyInjectionModule or an IServiceCollection extension, so applications don’t wire classes by hand:

services.AddLocalEventBus();
services.AddSnsMessageBroker(new AwsMessagingOptions("eu-west-1", "123456789012"));
services.AddSqsMessageBroker(new AwsMessagingOptions("eu-west-1", "123456789012"));
services.AddPostgresHealthReports();

or, as modules, with options read from the application’s own configuration:

services
    .UseModule(
        new ModuleSnsMessageBroker(config => new AwsMessagingOptions(config["Aws:Region"]!, config["Aws:AccountId"]!)),
        configuration,
        environment)
    .UseModule<ModulePostgresHealthReport>(configuration, environment);

Modules never assume a configuration section or settings type: options always come from the application. See Dependency-injection modules for the modules each package ships.

Picking packages by workload

You are building Start with
A REST API (Kestrel or AWS Lambda) Web, plus Testing.Web for tests
A GraphQL API Web.GraphQL
A Blazor WebApp Web.Ui and the Building UIs guide
An AWS Lambda job Hosting
An EC2/systemd worker Hosting.Workers
Relational persistence A provider: Postgres, Oracle or Mysql. See Database Providers
Messaging over SNS/SQS Infrastructure.Messaging.Aws
A new solution from scratch The anarchy-toolkit tool and Automation.Build

Every host registers Configuration’s ModuleLibConfiguration, which brings settings binding, secrets and the telemetry registration (AppTelemetry, correlation IDs) in one module. Not sure which packages you need? See Which package do I need?.

Plugging in your organization’s conventions

Organization-specific behavior is not part of the toolkit. Organizations plug their conventions into its extension points instead: logging providers, an OTLP exporter or an IMetricRecorder registered in DI (packaged as a ModuleTelemetryBase) for logs and metrics; options and constructor parameters; and ConfigureAppConfiguration hooks for configuration sources such as the AWS Parameter Store. See Your company’s setup.

Domain code (task orchestration, concrete repositories and clients, domain event payloads, message destinations, Swagger scopes, UI environment URLs) belongs in the consuming applications, not in the toolkit. Generic code takes strings and generic parameters instead of domain enums; enum overloads convert values with EnumExtension.ToDescription() (see Enum Conventions). Entities are marked with IEntity/IPersistedEntity.

Assertions in tests

The toolkit uses AwesomeAssertions rather than FluentAssertions. Only the Anarchy.Toolkit.Testing* packages depend on it, so production packages bring no assertion library into your application.