NathanFlurry

10 ms·

31.
by NathanFlurry 1y ago
This post did not mention the "external storage backend." It's assumed that the "external storage backend" is Google Cloud Storage, since they also use it for Durable Objects storage: https://youtu.be&#x2
32.
Faster route propagation by rewriting our Traefik gateway in Rust(rivet.gg)
4 points by NathanFlurry 1y ago|1 comments
33.
by NathanFlurry 1y ago
Does this example list help? https://github.com/rivet-gg/actor-core?tab=readme-ov-file#ex... > I'm also curious how the service handles multiple requests to the same state. That's the key part of ActorCore
34.
by NathanFlurry 1y ago
Thank you!
35.
by NathanFlurry 1y ago
> I don't quite get the concept yet. The details are kinda slim. Would be helpful to learn more. From looking at one of the examples, can you elaborate a bit on what doesn't make sense? Or is this more broadly how it works arch
36.
by NathanFlurry 1y ago
Appreciate the kind words! There’s definitely a lot of inspiration from Erlang. We’re far from the first actor-ish framework, but we’re hoping ActorCore sticks by working seamlessly with existing tools, instead of forcing people to learn a
37.
by NathanFlurry 1y ago
Appreciate the kind words! I see ActorCore as picking up on PartyKits vision where they left off after acquisition by Cloudflare. Here's a few of the few things we've added to ActorCore: - Full TypeScript type safety for calling a
38.
by NathanFlurry 1y ago
I've been enjoying watching you build this on X – nice work.
39.
Show HN: ActorCore – Stateful serverless framework that runs anywhere(github.com)
77 points by NathanFlurry 1y ago|12 comments
40.
by NathanFlurry 2y ago
Can you elaborate on both of these issues? Vanilla SQLite solved multiple writers a long time ago when they introduced WAL in 2010. Does Turso not support this? Is the issue with foreign keys that they're not enabled by default?
41.
by NathanFlurry 2y ago
Neat! How does this differ from KSQL?
42.
Considering a W3C Standard for Stateful Serverless(rivet.gg)
2 points by NathanFlurry 2y ago|0 comments
43.
by NathanFlurry 2y ago
Yep. Most designs I've seen put user profiles under a different table which requires a separate query.
44.
by NathanFlurry 2y ago
Author here! I agree it's very similar to the actor model, but I kept the article's scope small, so I didn’t cover that. In fact – Durable Objects talks a bit about its parallels with the actor model here: https://devel
45.
by NathanFlurry 2y ago
Author here, love this take. I've chatted with a few medium-sized companies looking at Durable Objects for this reason. DB-per-tentant removes much of the need for another dedicated team to provision & maintain infrastructure for t
46.
by NathanFlurry 2y ago
Fair point, noted.
47.
by NathanFlurry 2y ago
Hopefully, it matures into a healthy open-source ecosystem that doesn’t rely on proprietary databases. More companies than people realize are already building and scaling with DO SQLite or Turso internally. Almost every company I've ta
48.
by NathanFlurry 2y ago
If you care only about serverless, databases like PlanetScale, CockroachDB Cloud, and DynamoDB work well. The biggest strength of using SQLite here is that it provides the benefits of a familiar SQL environment with the scaling benefits of
49.
by NathanFlurry 2y ago
The two tables are intended to be part of the same "chat" partition (ie SQLite database). You can join them with a native SQLite query. Seems I should make this more clear. Cheers
50.
by NathanFlurry 2y ago
Author here. To clarify — is your concern that the only scaling options I listed are proprietary services? If so, I completely agree. This article was inspired by a tool we're building internally, based on the same architecture. We kne
51.
by NathanFlurry 2y ago
This seems to be the biggest hesitation I've heard over and over by far. There absolutely needs to be a good story here for both (a) ad-hoc cross-partition queries and (b) automatically building a datalake without having to know what E
52.
by NathanFlurry 2y ago
Great Scott!
53.
by NathanFlurry 2y ago
Yep. Nile ( https://www.thenile.dev/ ) is trying to address this use case with a fully isolated PG databases. Though, I don't know how they handle scaling/sharding.
54.
by NathanFlurry 2y ago
DuckDB crushes SQLite in heavy data workloads according to ClickBench by 915x. (Link below since it's looong.) DuckDB also has a WASM target: https://duckdb.org/docs/stable/clients/wasm/overview.html
55.
by NathanFlurry 2y ago
I think the other comments have the application-level approaches covered. However, I suspect the infrastructure will provide this natively as it matures: - Cloudflare will probably eventually add read replicas for Durable Objects. They&#x27
56.
by NathanFlurry 2y ago
Author here. Agreed — I think adding some comparisons to other database partitioning strategies would be helpful. My 2 cents, specifically about manually partitioning Postgres/MySQL (rather than using something like Citus or Vitess): S
57.
by NathanFlurry 2y ago
I (sort of) disagree. Cassandra- & DynamoDB-based systems which are also partitioned do fine without a central OLTP DB. Wrote a bit about it here: https://news.ycombinator.com/item?id=43246212
58.
by NathanFlurry 2y ago
> Is it even realistic to depend on transactional guarantees, with hundreds of services hammering the DB(s) more or less concurrently? If a single request frequently touches multiple partitions, your use cases may not work well. It'
59.
by NathanFlurry 2y ago
> The obvious caveat here is any situation where you need global tables A lot of people still end up storing data that's not frequently updated in a traditional OLTP database like Postgres. However: I think it always helps to think
60.
by NathanFlurry 2y ago
This. > In this case I think you can let them become inconsistent in the face of, e.g., write errors. For devs using CF Durable Objects, people frequently use CF Queues or CF Workflows to ensure that everything is eventually consistent w

More ›