DaanHoogland commented on issue #6778: URL: https://github.com/apache/cloudstack/issues/6778#issuecomment-1696844806
Yes > The most straightforward way is probably to just make the existing code aware that there can be more than one, and that would be fine for a small number. but that would be hard to maintain, any change would be at all calling locations. > If we want scalability (say we wanted dozens of implementations), maybe a sub/pub model would work better. I was under the impression that we had that but it is obviously crippled. I think we should grow to that. > I have a hard time imagining anyone would need many implementations. I think we are realistically talking publishing events to maybe two or three types of event bus. but two of three of varying types (plus internal) will make for a good justification of pub/sub. I will look into how much effort it will be to migrate to that. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
