Message bus object type for message queues and events
Garik Hakopian
isnt that just the store object? whats the added benefit in having another object type?
Jacob Shadbolt
Garik Hakopian There are 2 problems here, 1) Visual (basically a store sideways) for the audience to understand it behaves different to a regular store. 2) Specific features for message queue/bus systems, such as showing queues, topics, functions within (similar to components but again more specific for showing that workflow). We've seen people struggle to manage the volume of topics with component objects.
Garik Hakopian
Jacob Shadbolt I think I understand the reasoning behind it but I don't think I agree with it. the visual part can be resolved with a store that has a servicebus icon, C4 is meant to be clean and mostly show what objects are by description not by object shapes, adding more shapes and object types can contribute to clutter. For your second argument I can't say I can relate, I have been able to draw any kind of bus structure with the store object. Why can't components be used to draw servicebus structures in a store object? I might be missing a scenario here.