Celebrating the experimental launch of hubs.neynar.com

Neynar

strong opinion, weakly held: there are always better choices than Replicator

- clients do not need complex joins
- 2 Hubs handle concurrency as well as 1 Postgres constantly drip-fed by Replicator
- tested APIs > rewriting logic in SQL
- backfill is too complex: distinct state layers in Hub, bullmq, redis, postgres

Join my frens in cacc club.

Unforgettable Hair /bcbhshow. FOSS at GH:artlu99.

PFP is a wingding 

Any client of even basic complexity will need joins IMO

likes building things • https://alexgrover.me/links

For example, the hot/new/top filters on Flink.

Neynar is using a replicator so I consider that to be the same thing as running your own.

Do you have an example of the type of join needed by a FC client?

My hypothesis: simple joins can be handled in python/JS/TS without a DB. Neynar has APIs for the more common joins that a client might need. Airstack has APIs for joins that involve off-Hub data.