Ponder Ship Week, Day 3: Cached indexing

Thanks to @kjs, Ponder now caches indexing progress across hot reloads and redeploys.

If you restart a fully cached app with no code changes, it goes live in ~2 seconds.

(1/6)

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

How does it work?

During the build step, Ponder analyzes your project code (config, schema, src/) and decides what can be served from the cache vs. what needs to be reindexed.

Once live, the indexing engine periodically flushes progress to the cache.

(3/6)

The coolest thing about Ponder's cache is that it's granular.

If you change the code of one indexing function, only that function and any functions that depend on it will reindex.

Btw, cache invalidation is hard and there might be bugs. Ping us if you see anything wonky!

(4/6)

We've invested heavily in static analysis. In our view, it's central to an end-game developer experience for EVM indexing.

Read the docs to learn more about how it works:
http://ponder.sh/docs/guides/caching-and-concurrency

(5/6)

We're hiring senior & staff-level engineers to work on Ponder and other unannounced projects. If this work sounds exciting, DM me.

Two more days of Ship Week to go - see you tomorrow, nerds!

Slow redeploys are a well-known pain point in blockchain indexing.

One of our goals is to solve the redeploy problem without compromising on flexibility (write arbitrary TypeScript) or local development (caching works locally). This release is a key step.

(2/6)

hypertext veteran • /mud core dev @lattice