Application patterns beyond the basics

Choose a guide when your application needs the behavior below. Start with the ticket desk tutorial if you have not yet created models, applied migrations and exposed a protected API.

Work and recovery

You need to…	Read	Boundary
Queue work outside a request	Background tasks	Ordinary tasks have their own retry and delivery contract.
Recover an authorized operation after failure	Durable Operations	Application mutations are atomic only within the supported same-database transaction boundary.
Reuse a persisted step result	Generic relations and persisted steps	DurableStep is evolving and is distinct from a durable Operation.
React to an individual model save or delete	Signals	A callback is not proof that the surrounding transaction committed.

For a working example that grows the tutorial application, follow background reports, then durable ticket resolution.

Data and application behavior

You need to…	Read
Reject or normalize input	Validation and serializer hooks
Define a custom field	Custom fields
Store files or send application email	Media and email
Select request language and timezone	Internationalization and timezones
Reference different model types	Generic relations

Testing and performance

Use testing for application fixtures and isolation boundaries, performance for measurement and query design, and query profiling for the available diagnostics.

The caching guide explains application-owned caching. Aksara does not provide a public general-purpose aksara.cache API.

These guides build on models, ViewSets and application boundaries. Consult stability before relying on an evolving or experimental surface, and the production guide when moving a working application into service.