This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-22
Channels
- # announcements (10)
- # babashka (40)
- # beginners (192)
- # calva (9)
- # cider (2)
- # clj-kondo (9)
- # clojure (69)
- # clojure-dev (15)
- # clojure-europe (29)
- # clojure-gamedev (6)
- # clojure-italy (2)
- # clojure-nl (41)
- # clojure-spec (49)
- # clojure-uk (11)
- # clojurescript (68)
- # conjure (1)
- # cryogen (20)
- # cursive (37)
- # data-oriented-programming (10)
- # data-science (4)
- # datahike (7)
- # datomic (8)
- # depstar (14)
- # emacs (7)
- # events (2)
- # figwheel-main (1)
- # fulcro (81)
- # honeysql (22)
- # hugsql (5)
- # juxt (3)
- # leiningen (8)
- # lsp (314)
- # malli (20)
- # meander (15)
- # membrane (20)
- # mid-cities-meetup (11)
- # practicalli (2)
- # reagent (2)
- # remote-jobs (2)
- # ring-swagger (1)
- # rum (3)
- # sci (21)
- # shadow-cljs (52)
- # startup-in-a-month (1)
- # testing (9)
- # tools-deps (41)
- # vim (8)
- # xtdb (4)
Q: I am using Cloud and provide an mullti-tenant application to a global audience. I want to minimise latency by letting customers use an AWS region close to them. I plan to support 3 regions for this but I currently have 1. I am wondering how I could allow customers to move regions i.e. replicate all their single-tenant data from one Datomic db to another (with the same schema) in a different region
Any gotchas or tips would be much appreciates. Or even just suggestions so that I am aware of options I haven’t thought of by my lonesome
The first ideas I had are full replication or on-demand replication at the app level i.e. I build my own export/diff tool. Or is it replication based on mutation events replayed in the 2 other dbs?
We would like to clone a database within a single storage (on-prem). Unfortunately backup-restore can’t do that for us due to it’s limitations [1]: > Backup and restore are not suitable for cloning of a database within a single storage. If you attempt to restore a database into a storage that already contains that database, but under a different name, the restore operation will fail. Are there any other existing ways to do that? Thank you. [1] https://docs.datomic.com/on-prem/operation/backup.html#limitations
We've experimented with replaying the reflog on a separate database, and even duplicating the underlying storage in order to duplicate/back it up. Both were a pain so we now use backup to a separate install, which is rather painless
Thanks