EventBus interface question

[mammenj]

I see EventBus has publish but not a subscribe?
Just curious how the events propagated to projects for querying?
I apologize if subscribe is defined somewhere else as I did not read the source code completely.

[mishudark]

Hi, for now, the project ends on the publish of events, I think subscribe should be done very easy, for example, nats and rbmq has nice client libs, but definitely, to have a built-in interface for subscribing should be a nice feature

[mammenj]

Would the Subscribe be something like below, your thoughts?

type EventBus interface {
	Subscribe(eventTopic string) (Event, error)
}

[mishudark]

I think it should be counterpart of publish interface

type Subscriber interface {
        Subscribe(bucket, subset string) (Event, error)
}

but I like the word topic probably instead of subset

[mammenj]

Thanks for the response, makes sense to have it as as a separate interface.
Do you want me to pull and request for merge to include this interface and its implementation ?

[mammenj]

How about something like this

type EventBus interface {
	Subscriber
	Publisher
}

type Subscriber interface {
        Subscribe(bucket, subset string) (Event, error)
}

type Publisher interface {
        Publish(event Event, bucket, subset string) error
}

[mishudark]

I like it, yes for sure, help is welcome :D