ENSNode Operations

Operating an ENSNode deployment requires understanding the key workloads that ENSNode is responsible for, as well as the best practices for managing and optimizing these workloads, including monitoring, scaling, and resource management.

Base requirements

Before you run ENSNode in any environment, you will need:

• PostgreSQL database with the pg_trgm extension available.
• RPC Provider access for each chain you want to index. High-throughput, low-latency RPCs are essential during the initial historical backfill.
• Disk space for ENSDb (anything from tens of gigabytes to several hundreds, depending on the selected ENS Namespace and activated ENSNode Plugins).
• Disk space for ENSRainbow (at least 55 GB for the searchlight label set).
• Co-located service instances for best performance. ENSIndexer, ENSRainbow, and ENSDb should be on the same local network, and ideally, in the same availability zone to minimize latency.

In this section

Key workloads Understand the resource demands behind each ENSNode workload.

ENSNode Scalability Architecture overview of how to scale ENSNode to handle a massive volume of requests.

ENSNode Monitoring Learn what to monitor and how to set up basic alerts.

Troubleshooting Common symptoms and how to resolve them.