We can have different services emit events to clients using pusher service
Clients can subscribe to the network's channel and receive events such as billing changes, and other concerns rather than relying on polling or other means.
This is an architectural question because I am unsure whether every service should be publishing to pusher service or if there is a better event-driven, async pattern here. This also brings into question whether we implement a local-first with a sync server.
We can have different services emit events to clients using `pusher service`
Clients can subscribe to the network's channel and receive events such as billing changes, and other concerns rather than relying on polling or other means.
This is an architectural question because I am unsure whether every service should be publishing to pusher service or if there is a better event-driven, async pattern here. This also brings into question whether we implement a local-first with a sync server.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We can have different services emit events to clients using
pusher serviceClients can subscribe to the network's channel and receive events such as billing changes, and other concerns rather than relying on polling or other means.
This is an architectural question because I am unsure whether every service should be publishing to pusher service or if there is a better event-driven, async pattern here. This also brings into question whether we implement a local-first with a sync server.