spring cloud stream multi api version

Hi @GreenRover,

Hope you’re doing well! I like @JamilAhmed’s idea of separating the logic of the current version vs. potentially 1+ legacy versions, but you have a great point with the potential for the current version not containing deprecated information.

How does your app receive the data? Is it delivered via a Solace topic to where you could just have multiple microservices receiving it? One for each version?

If the data isn’t already arriving on a solace topic you could obviously publish it to a topic to allow for fan-out to happen outside of your app, or if you prefer to do it inside your app then my gut reaction is that this feels like a Spring Integration type challenge and you could either leverage an internal spring integration pubsub channel or even use a Spring Integration Flow as a function.

I’ll try to think more about this later and let you know if I think of a more elegant solution.