Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subscriptions #20

Open
gedw99 opened this issue Sep 29, 2024 · 0 comments
Open

Subscriptions #20

gedw99 opened this issue Sep 29, 2024 · 0 comments

Comments

@gedw99
Copy link

gedw99 commented Sep 29, 2024

I dont think this does subscriptions ?

A SQL Query that is a subscription. SO if the results of the Query changes, then all Clients are told over HTTP ( maybe SSE ) or maybe actually NATS.

working out what mutation to the DB, effects what Queries is a tough one.

so maybe a brute force approach of having scored procedures. In other work all possible Queries are told to the system. In fact they could be stored in NATS, and also synced, but that another story.
The idea is that for each possible query, a backend taks just runs them every few seconds, with all possible params, and then tells clients when it's changed. It's nuts because the possible parmataters are infinite, but what is they were not ? For example a classic query of "give me all books by this author". The number of authors is know, because its also in the db.

what will not work is a query where the param is time or date based, like "give me all books by author X, where the book was published after 01-02-2024".

It interesting that NATS streams know the history of every possible query. Thats means the cardinality of possible queries is known. mhhh

@gedw99 gedw99 changed the title Subscriptuiions Subscriptions Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant