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
(This may be more of a 'pro tip' than something that needs to be baked into Chasqui, FYI)
At RFX, we've moved to versioning our event names. So, for example, you want to run some handler code whenever an asset data object is created. We would route/subscribe/publish an event as 'assets:created_v1' - where 'assets' is the channel and 'created_v1' is the event name. All this does is further decouple code. If we want to change the payload or handler code for that event, we just start publishing a '_v2' version of the event as needed. Sometimes the publisher may publish both the v1 and v2 events at the same time. The goal is allowing a way to safely upgrade all (or just some) of the event subscribers to the new version without breaking the old subscribers (even temporarily).
Anyway, this could be baked formally into Chasqui's event API or it could just be a 'protip' on naming events. Just wanted to throw it out there and see what you think. Let me know if you have any questions. Thanks!
The text was updated successfully, but these errors were encountered:
(This may be more of a 'pro tip' than something that needs to be baked into Chasqui, FYI)
At RFX, we've moved to versioning our event names. So, for example, you want to run some handler code whenever an asset data object is created. We would route/subscribe/publish an event as 'assets:created_v1' - where 'assets' is the channel and 'created_v1' is the event name. All this does is further decouple code. If we want to change the payload or handler code for that event, we just start publishing a '_v2' version of the event as needed. Sometimes the publisher may publish both the v1 and v2 events at the same time. The goal is allowing a way to safely upgrade all (or just some) of the event subscribers to the new version without breaking the old subscribers (even temporarily).
Anyway, this could be baked formally into Chasqui's event API or it could just be a 'protip' on naming events. Just wanted to throw it out there and see what you think. Let me know if you have any questions. Thanks!
The text was updated successfully, but these errors were encountered: