This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-08
Channels
- # announcements (9)
- # babashka (17)
- # beginners (26)
- # biff (2)
- # calva (5)
- # cider (11)
- # clara (6)
- # clojure (48)
- # clojure-europe (34)
- # clojure-nl (1)
- # clojure-norway (34)
- # clojure-uk (2)
- # clojurescript (22)
- # clr (11)
- # code-reviews (5)
- # conjure (3)
- # datomic (26)
- # emacs (14)
- # fulcro (10)
- # hyperfiddle (70)
- # lsp (34)
- # malli (5)
- # missionary (5)
- # off-topic (34)
- # releases (1)
- # shadow-cljs (19)
- # tree-sitter (1)
- # xtdb (25)
Hey. I was reading the Content Library section of your webpage: https://biffweb.com/docs/library/ Why do you consider "Scaling out with Redis + load balancer" to be scaling out? It would work the same way as Slack and it would just shard the data. But what will happen if the users will want to interact with the inter-shard users? Then it won't work. I don't yet know how to address this but I haven't seen a connector to let's say Cassandra if we're really talking about extreme cases of scaling out. What do you think about this?
The load balancer lets you scale out to multiple web servers, and if you use Redis as a job queue then you can scale out to multiple workers. They'd all still operate on the same XTDB instance/set of data. You'd need to use e.g. Postgres as the storage backend instead of the local filesystem. If you need to scale a lot you can use Kafka as the storage backend. And once you you need to scale beyond that, you can hire someone to do it for you 😉