Similar to how the KV and Object Store APIs have prefixes, this is desirable to prevent subject clashes with application managed subjects.
For example, an event store r.EventStore("orders").Create(nil) would create a stream bound to rita.events.sourced.orders.>. This seemingly long prefix is due to other future plans to leverage streams, such as rita.events.received and rita.events.published with would be streams to used for receiving external events (via some integration or other Rita context) and publishing events to be consumed by other boundaries, respectively.
Similar to how the KV and Object Store APIs have prefixes, this is desirable to prevent subject clashes with application managed subjects.
For example, an event store
r.EventStore("orders").Create(nil)would create a stream bound torita.events.sourced.orders.>. This seemingly long prefix is due to other future plans to leverage streams, such asrita.events.receivedandrita.events.publishedwith would be streams to used for receiving external events (via some integration or other Rita context) and publishing events to be consumed by other boundaries, respectively.