Are GraphQL subscriptions supported by ComposeDB?

Devtools ComposeDB
1

GraphQL servers frequently support subscriptions which allow receiving changes in real time.

Does the ComposeDB server support these?

2

Hey @dysbulic. As of now, subscriptions are not supported, but it’s something that we plan to add in the future.

1 Like
3

Hey @dysbulic,

As a workaround, I use PostgreSQL CDC, Kafka Connect, and Apache Kafka to achieve a form of pub/sub functionality. Then I handle my subscription logic separately.

I believe tasks like these will become easier once the Ceramic API is released.

3 Likes
4

Could you perhaps add this to the public roadmap on GitHub? :slight_smile:

5

Hey @m0ar. Will definitely share some updates on the updated roadmap soon. Will make sure we add an update about the subscriptions there too.

6

Hello @Justina @dysbulic @seref,

Any updates here?

I was planning to use Data Feed Api to achieve some kind of pub/sub functionality, concretely one node modifies information/model, and then clients listening to the ceramic node indexing that model directly receives this update without the need of querying.

This would be the best approach today, right? As I see this post was created year and a half ago and probably we have new ways to do it?

Just wanted to verify that I am following the right path.

Thanks in advance!

7

Hi @Eloy,
Please note that ComposeDB is deprecated in favor of using ceramic-one directly. Please see this post for more context: The Future of Ceramic: Focusing on Recall

1 Like
8

I see, thanks a lot @spencer.

So I should not use this repository either because it is using js-ceramic that will be deprecated, right? So the repo which is recommended here would need to be updated, correct?

I also see that the repo is using an old ceramic-one version, so it leads to failures if I am not wrong.

Thanks in advance!

9

Yeah that’s right, looks like the docs might be a bit outdated here