Open ryan-mars opened 3 years ago
We concluded the naming of events could serve as name spacing. If Reservations and Scheduling both had an event named FlightUpdated
they should instead be named ReservationFlightUpdated
or SchedulingFlightUpdated
respectively.
Is this sufficient for now? What's next?
Two identically named events in two different services which share events should not be confused at runtime based upon
__typename
alone.