Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

versioned events?? #18

Open
kellyredding opened this issue Aug 24, 2015 · 0 comments
Open

versioned events?? #18

kellyredding opened this issue Aug 24, 2015 · 0 comments
Labels
Milestone

Comments

@kellyredding
Copy link

(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!

@jbgo jbgo added the feature label Aug 25, 2015
@jbgo jbgo added this to the v1 release milestone Aug 25, 2015
@jbgo jbgo modified the milestones: post v1, v1 release Sep 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants