A place for developers to talk about building on Farcaster.

/dev

Ponder

Should Ponder replace SQLite with PGlite (pglite.dev) as the dev database? 

Pros:
1) Less magic/astonishment ("wait, what database am I using rn?")
2) Simpler schema definition API (currently stuck with the subset of stuff that both PG and SQLite support)

Going all-in on Postgres was the single best decision we made in 2024.

Much simpler, with no regression to the quickstart / local dev experience (thanks to PGlite). Obvious in retrospect.

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

🦀 /foundry @paradigm | founding engineer /ithaca

Good point, I was wondering because I had read that Nansen and Goldsky are using it in their infrastructure but seemingly in an OLAP way

Good point, I was wondering because I had read that Nansen and Goldsky are using it in their infrastructure but seemingly in an OLAP way

https://clickhouse.com/blog/clickhouse-redpanda-architecture-with-goldsky

https://clickhouse.com/blog/unlocking-the-power-of-onchain-analytics-how-nansen-transformed-their-data-infrastructure-with-clickhouse-cloud

Big fan of ClickHouse, it's unbeatable for some use cases like structured logs.

It would be a bad fit for Ponder's user-facing database, though. Indexing workloads can be OLTP-y and do many key-value / unique index lookups, which are anathema for a column-oriented database.