Recent submissions

Comment · 2 years ago
Comment · 2 years ago
sure, I would be happy to hear more about it. Let me know how to contact you.
Comment · 2 years ago
Thanks, super helpful. re Cloudflare, are you using them to reduce latency? what about a centralized database?
Comment · 2 years ago
Expiration-based cache (e.g., 3 seconds) is not acceptable in this case, and more than that will reduce the load on the server + db dramatically.

Imaging subscribing to SQL query not just for a table; isn't it very complicated?

Comment · 2 years ago
It's super simple for a simple demo app, not easy for a large scale.
Comment · 2 years ago
Thanks! Electric looks great! though I'm wondering how it works in scale. I'm using Postgres and have some heavy queries, would be great to cache\materizlized the results instead of re-run them every time for every user, or for returning users without any change in the data.
Comment · 2 years ago
Thank you for the detailed answer, you're awesome.

Electric-SQL, Convex, and Triplit are definitely relevant, and I'll dive deep into understanding their pros and cons. In the meantime, I found another relevant one: https://squid.cloud/, which has a slightly different approach, more like full BAAS.

On one end, it can save me some time; on another, it's another stack my R&D needs to be familiar with.

Comment · 2 years ago
It looks very relevant to my problem! Have you used it? is it production-ready?
Comment · 2 years ago
Agree.
Comment · 2 years ago
Thanks! > It's fairly straightforward to write a websocket endpoint in whatever backend you have

It indeed solves half of the problem, but managing websockets for thousands of users is not that trivial IMO

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton