Arc.Core
Use Cratis.Arc.Core when you want commands, queries, validation, authorization, identity details, and tenant context without the ASP.NET Core host. A console application or worker can expose HTTP endpoints through ArcApplication and .NET’s HttpListener.
Start with a working service
Section titled “Start with a working service”The getting-started checkpoint runs a command and query using only Core. Read the host comparison to decide whether Core or the Cratis.Arc ASP.NET integration fits your application. Performance and Native AOT compatibility require testing your actual dependencies and publish configuration; they are not guaranteed by choosing Core.
Topics
Section titled “Topics”- Overview — capabilities, boundaries, and host choice.
- Getting started — register, activate, and run.
- Endpoint mapping — manual GET/POST endpoints.
- Static files — public assets and SPA fallback.
- Authentication — trusted principals and forwarded-header prerequisites.
- Authorization — pipeline authentication and role checks.
- OpenAPI — built-in lightweight route documentation.
- Invariant culture — default culture configuration.
Shared features and optional integrations
Section titled “Shared features and optional integrations”Commands, queries, identity, and tenancy belong to standalone Arc. Review configuration and anonymous discovery defaults before deployment.
Add MongoDB or EF Core for persistence without requiring event sourcing. Add Chronicle only when you want its event log, projections, and integration behavior. These integrations have their own packages and setup requirements.