Edge computing for social apps: what actually makes sense today
Q1Everyone's talking about edge computing, but in the social product space I see a lot of hype and not much critical thinking. Moving your API to the edge doesn't magically make your app faster if 90% of your latency is database queries to a centralized PostgreSQL. What social app workloads actually benefit from edge?
Q2What about CRDTs for edge-native social data? I've been exploring using CRDTs for things like read receipts, typing indicators, and reaction counts — data where eventual consistency is fine.