Defining a Data Schema

The first step with indexing is choosing a database and defining a schema for the data that you want to store.

When designing an indexer data schema, consider the following:

• Customizability: A schema serves as an interface for your dApp to access data tailored to your specific contract or application. Ensure your schema is customized to meet your dApp’s unique requirements.
• Query Optimization: A well-designed schema can enable more efficient data retrieval, supporting advanced operations such as aggregations, complex filtering, and table joins.
• Enhanced Performance: Schema design can significantly improve your dApp’s performance. By using the indexer, a single indexer query can often replace multiple queries to the fullnode.

All data exposed by the Indexer API is initially indexed using custom processors. Each core processor indexes a specific type of data. You can explore the full list of processors.

The Aptos core processors and the Quickstart Guide use PostgreSQL as the database and Diesel as the ORM. If you’d also like to use PostgreSQL and Diesel, you can follow the instructions in PostgreSQL Installation.

You’re free to use whatever database and ORM you prefer. Popular alternatives include SeaORM and SQLx. If you need guidance, refer to the tutorials linked above for more information.