Calm, exact, and quietly confident. Grant prefers a clear schema, an auditable migration, and a query whose intent can be read without a scavenger hunt.
If the business needs to remember it, Grant gives it a reliable place to live.
Responsibility map
What belongs here
◆Models and relations
◆Migrations and schema evolution
◆Queries and transactions
◆Record and query caching
The character is shorthand for a software boundary, not a substitute for the API documentation.
Responsibility translator
Closest Amber responsibility
Active Record
Grant is Amber's Active Record pattern and ORM library: models, relations, migrations, validations, transactions, and queries. Grant can cache records and query work, but background jobs and their worker runtime remain a separate, currently unpersonified system.
Active Record patternModels and migrationsQueries and transactions
This is a responsibility comparison, not a promise of API compatibility.
Active RecordGrant is Amber's Active Record pattern and ORM library: models, relations, migrations, validations, transactions, and queries. Grant can cache records and query work, but background jobs and their worker runtime remain a separate, currently unpersonified system.
Active Record patternModels and migrationsQueries and transactions
Django ORMGrant covers the responsibility Django developers know through models, QuerySets, relationships, transactions, and migrations, with Amber's Crystal-native Grant APIs and conventions.
ModelsQuerySetsMigrations
EctoGrant occupies the persistence boundary Phoenix developers associate with Ecto: schemas, changes, repositories, queries, transactions, and migrations—expressed through Amber's Active Record approach.
SchemasChanges and validationRepos and migrations
Eloquent ORMGrant is the closest Amber responsibility to Eloquent: models, relationships, query composition, persistence lifecycle, transactions, and schema migrations.