Skip to main content
Sinks define the destination of your data. Mirror supports a variety of sinks, from traditional databases optimized for querying and analysis to intermediate storage layers like Kafka and S3 that facilitate further integration into your data stack.

Available Sinks

Mirror supports a wide range of sinks optimized for different use cases, from real-time querying to analytics and data integration:

What should I use?

For APIs for apps

For sub-second queries, typically you would choose a database that has row-based storage (i.e. it stores each row as it is instead of applying any sort of compression). The drawbacks are that they take more space. This means large, non-indexed scans can take longer and storage costs can be higher.
  1. Postgres is the gold standard for application databases. It can scale almost infinitely with some management (You can use a Goldsky hosted version so you don’t have to worrry about scaling), and can support very fast point-lookups with proper indexing. If you require super fast lookups by transaction_hash or a specific column, Postgres is a very safe choice to start with. It’s great as a backend for live data APIs. However, it can be slow for analytics queries with a lot of aggregations. For that, you may want to look for an analytical database. Great hosted solutions for Postgres include NeonDB, AWS Aurora, and GCP CloudSQL.
  2. Elasticsearch is a no-sql database that allows for blazing fast lookups and searches. Elasticsearch is built around super-fast non-indexed scanning, meaning it can look at every single record to find the one you want. As a result, you can do queries like fuzzy matches and wildcard lookups with millisecond latency. Common applications include search on multiple columns, ‘instant’ auto-complete, and more.

For Analytics

  1. ClickHouse is a very efficient choice for storage. You can store the entire Ethereum blockchain and pay around $50 in storage. We recommend considering ClickHouse as an alternative to Snowflake or BigQuery - it supports many of the same use cases, and has additional features such as materialized views. We’ve seen our customers save tens of thousands of dollars using Goldsky and ClickHouse as a solution. The pricing for managing ClickHouse is based on storage cost, then compute cost. The compute cost is constant and isn’t based on the amount of data scanned, so you can run concurrent queries without increasing cost.