There is one way: Send meeting invites to all teams. After 101 meetings, post your maintenance banner, and everyone hits the release button at the same time. Or...
Reminds me a bit of a Strangler-Fig-like approach only with events involved for a gradual migration. One risk is that the adapter becomes a permanent component. For this, I'd suggest keeping a hard deadline at some point when it will be decommissioned.
I like this. Typically I’ve made the message backwards compatible or, for major changes, updated the consumers to accept both formats before updating the producers.
This is a simple way to decouple all of it.
Now just need to make sure the consumers get updated and we don’t get stuck with the adapter forever.
Backward compatibility is my favorite approach. As you mentioned, I like this approach because I don't need to deal with the producer anymore, so consumers can now change at their own pace.
I like this. Typically I’ve made the message backwards compatible or, for major changes, updated the consumers to accept both formats before updating the producers.
This is a simple way to decouple all of it.
Now just need to make sure the consumers get updated and we don’t get stuck with the adapter forever.
Great approach Raul.
Reminds me a bit of a Strangler-Fig-like approach only with events involved for a gradual migration. One risk is that the adapter becomes a permanent component. For this, I'd suggest keeping a hard deadline at some point when it will be decommissioned.
Also, thanks for the mention brother!
That's a great point, Saurabh; the risk of a "temporary fix" is a reality.
A hard deadline with a follow-up is a must!
That's a great article, Raul! And thank you for the mention!
Thanks, Petar!
Keep them coming.
I like this. Typically I’ve made the message backwards compatible or, for major changes, updated the consumers to accept both formats before updating the producers.
This is a simple way to decouple all of it.
Now just need to make sure the consumers get updated and we don’t get stuck with the adapter forever.
Exactly, Mike.
Backward compatibility is my favorite approach. As you mentioned, I like this approach because I don't need to deal with the producer anymore, so consumers can now change at their own pace.
Thanks!
I like this. Typically I’ve made the message backwards compatible or, for major changes, updated the consumers to accept both formats before updating the producers.
This is a simple way to decouple all of it.
Now just need to make sure the consumers get updated and we don’t get stuck with the adapter forever.
A solid breakdown my friend! Keep these bangers coming!
Thanks, Daniel!!!
Consumer1 has read till message number 10 from the old topic.
Now, Consumer1 is migrated, and meanwhile message 11, message 12, message 13 are produced to the new topic.
Now, how does Consumer1 read the messages from message 11 from the new topic?