Content
@
0 reply
0 recast
0 reaction
artlu is on lunchbreak!
@artlu
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
3 replies
1 recast
1 reaction
alex
@alexgrover.eth
Any client of even basic complexity will need joins IMO
1 reply
0 recast
1 reaction
artlu is on lunchbreak!
@artlu
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.
1 reply
0 recast
0 reaction
alex
@alexgrover.eth
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.
1 reply
0 recast
0 reaction
