Content
@
0 reply
0 recast
0 reaction
artlu
@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
artlu
@artlu
I feel I should have dived into the Hub APIs first (slightly steeper idiosyncratic learning curve), rather than jumping straight to SQL: a flat non-idiosyncratic learning curve, followed by more difficult data+infra issues to reason about. Is anyone thrilled that they chose to base their FC client on Replicator?
0 reply
0 recast
0 reaction
