This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-08-10
Channels
- # announcements (1)
- # babashka (16)
- # beginners (42)
- # calva (6)
- # clj-kondo (7)
- # clj-yaml (13)
- # cljdoc (7)
- # clojure (34)
- # clojure-bay-area (7)
- # clojure-dev (14)
- # clojure-europe (10)
- # clojure-nl (1)
- # clojure-norway (26)
- # clojure-sweden (91)
- # clojurescript (7)
- # datalevin (3)
- # datomic (35)
- # dev-tooling (8)
- # emacs (22)
- # graphql (1)
- # honeysql (13)
- # hyperfiddle (28)
- # introduce-yourself (1)
- # jobs-discuss (11)
- # juxt (4)
- # lsp (21)
- # off-topic (7)
- # reagent (4)
- # releases (3)
- # spacemacs (16)
- # xtdb (4)
- # yamlscript (2)
Hi, from an architecture POV, are there best practices/references/discussions about horizontal database scaling ? I’d like to foresee the dynamics and risks when we scale. [Q1] Also as Datalevin is an operational database, if we want to sync data between database replicas, what might be the approach? [Q2] Is event-driven architecture one of it?
Q1, depends on your use case. There are a few options now. One db per user is good for some use cases. There are limits on the number of dbs you can open in one process depending on memory, OS, etc; a couple of thousands normally. Another option is to use the server mode. The distributed mode is on the roadmap, but it is way down the road