You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2017. It is now read-only.
What kind of events are we talking about here? Is the client listening for events regarding a specific service or can services listen to other services lifecycle events?
Request cycle implies some sort of interceptor design and then it could be used to inject custom filters and such. Is the idea that a given client can register custom callbacks (event listeners i guess) or are the service implementor responsible for it?
I am not 100% convinced that we need events. The idea is that we might use an event early in the life cycle of a request to fetch data or prepare for a data operation later in the life cycle of the same request. Technically though this could be just another sky net service. So adding events as a concept may be over complicating things. I am happy to entertain discussion on this...
What kind of events are we talking about here? Is the client listening for events regarding a specific service or can services listen to other services lifecycle events?
Request cycle implies some sort of interceptor design and then it could be used to inject custom filters and such. Is the idea that a given client can register custom callbacks (event listeners i guess) or are the service implementor responsible for it?
This way its getting rather deep into orchestration land which may or may not be good thing. It can clearly complicate things but if the use-case warrants it perhaps its worth it.
I haven't looked into how the other type of functions like stats collection etc monitoring and what not are implemented (arr they yet?) but possibly an interceptor approach could be used for these things and when that is in place the event functionality could come by itself.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Create named events based on lifecycle. Request start, complete, etc.
Create interface for event notification.
create implementation for event notification using a pub/sub (topic) message queue.
The text was updated successfully, but these errors were encountered: