Repository navigation
Partie Index
SteffenBlake edited this page Sep 28, 2026
·
3 revisions
Partie connects typed query and command handlers to application operations. Requests carry input, contexts supply dependencies, and Providers and Parties add values and shared behavior around handlers.
- Requests: define query and command input.
- Handlers: implement operations, choose result types, and pass cancellation to services.
- Contexts: receive services, provided values, earlier values, and registration parameters.
- Providers: create values on demand and share them within an invocation.
- Parties: run ordered steps, stop an operation early, and wrap downstream work.
- Generic matching: apply reusable behavior to selected request and result types.
- Bundles: register related steps together and forward configuration.
- Results: return values and failures, inspect cases, and transform results.
- Unit of work: commit and roll back command resources.
See ASP.NET Core for HTTP binding, routes, policies, response mapping, and integration bundles. Start with CQRS routing with Partie for package installation and your first endpoint.
- Home
- Getting started
-
Package guides
- Partie
- Expo
-
Mise
- Database setup
- Table mappings
- Aliases
- Relationships
- Result rows
- SQL interpolation
- Queries
- Filtering
- Joins
- Aggregation
- Paging and ordering
- Subqueries
- Set operations
- Common table expressions
- Readers
- Streaming
- Writers
- Inserts
- Updates
- Deletes
- Returned rows
- Custom SQL and procedures
- Transactions
- Resource lifetimes
- Database dialects
- Diagnostics
- Integrations
- Recipes
- Reference
- Troubleshooting
- Development