bruchim

7 ms·

1.
A Realtime Competitor Analysis(ably.com)
1 points by bruchim 2y ago|0 comments
2.
GraphQL Live Query, How To?(github.com)
1 points by bruchim 2y ago|1 comments
3.
by bruchim 2y ago
Is there an official production-ready solution for getting the 'Live Query' unofficial feature working? (I'm not talking about 'subscription') I've found some [1] [2] [3], but they're either archived or no
4.
Ask HN: Reactive and LocalFirst GraphQL Platform?
1 points by bruchim 2y ago|0 comments
5.
Ask HN: Local First with GraphQL?(plain.com)
1 points by bruchim 2y ago|0 comments
6.
by bruchim 2y ago
sure, I would be happy to hear more about it. Let me know how to contact you.
7.
by bruchim 2y ago
Thanks, super helpful. re Cloudflare, are you using them to reduce latency? what about a centralized database?
8.
by bruchim 2y 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?
9.
by bruchim 2y ago
It's super simple for a simple demo app, not easy for a large scale.
10.
by bruchim 2y 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 re
11.
by bruchim 2y 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:/
12.
by bruchim 2y ago
It looks very relevant to my problem! Have you used it? is it production-ready?
13.
by bruchim 2y ago
Agree.
14.
by bruchim 2y 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
15.
by bruchim 2y ago
Very interesting, thank you. I looks like a layer on top of your database, not a standalone baas, which is great. Have you used it in production?
16.
by bruchim 2y ago
just thinking about implementing incremental materialized views and maintaining web sockets with clients makes me nervous, but maybe I'm the only one. Have you implemented such a solution e2e? from db to frontend?
17.
Ask HN: How Can I Make My Front End React to Database Changes in Real-Time?
38 points by bruchim 2y ago|54 comments
18.
by bruchim 2y ago
Specifically about performance, have you tried to solve it with any caching mechanism or any other out-of-the-box optimization?
19.
by bruchim 2y ago
We are using Apollo on top of our Postgres db, which is also used for other CRUD REST APIs. I'm basically looking for more perspective of other teams, if they are feeling the same after migrating to graphQL (the same query in simple no
20.
by bruchim 2y ago
TBH, I summarized here almost a year of a process into a single paragraph, maybe it's my bad. A few engineers with good performance minds have already benchmarked and improved some of the queries, and we learned a lot from the process.
21.
Ask HN: GraphQL Performance Issues, Am I the Only One?
1 points by bruchim 2y ago|7 comments
22.
by bruchim 3y ago
D1 is currently limited to 100 MB, and I'm doubtful it's meant to be a complete database. As I understand it, it's more for "manual cache" purposes and not for hosting everything there (think about 100 TB of data).
23.
Ask HN: Edge Computing, a Half-Solved Puzzle?
3 points by bruchim 3y ago|3 comments