This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-07
Channels
- # announcements (1)
- # architecture (9)
- # babashka (3)
- # calva (10)
- # clj-http (13)
- # clj-kondo (11)
- # clojure (23)
- # clojure-europe (11)
- # clojure-nl (1)
- # clojure-norway (112)
- # clojure-uk (4)
- # clojuredesign-podcast (8)
- # clojurescript (10)
- # core-async (5)
- # cursive (7)
- # data-science (15)
- # datascript (2)
- # datomic (29)
- # emacs (5)
- # events (1)
- # hugsql (1)
- # hyperfiddle (9)
- # midje (1)
- # missionary (3)
- # music (1)
- # off-topic (34)
- # polylith (1)
- # re-frame (16)
- # shadow-cljs (117)
- # squint (19)
- # yamlscript (1)
I'm looking forward to using missionary in my project, but as a beginner I have some doubts. Imagine a situation where there is a database in the backend with a large amount of data.The frontend has multiple users connecting at the same time, but the content viewed by each user is different. In other words, the frontend only obtains a subset of the database for display. My problem is that when the database changes, I only want to trigger the relevant parts without propagating to all, but what should I do?
This is quite vague, you have an architecture problem to solve and missionary won't help you with that.
@U01SBSXRRH6 Agree. It's just that I didn't fully understand missionary, so I was worried that I would miss its ability to handle this problem.