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

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.

pglite is great! starting one process that hosts the app, database and relevant services (including task queue that pg can handle well) is magical

For my project a long time ago, I ditched as well sqlite because reasons. The change to postgres has been always amazing. Zero regrets so far.

We’re they’re any not great things about the change?

for your production use case, a "proper" rdbms like PostgreSQL is what makes sense