> But none of that changes that the service is responsible for a > particular set of data. Service B better not be messing with Service > A's data via the data repository layer. If Service B needs something > done, it needs to use Service A's operations, not mess directly with > Service A's data. Reservation data is defined, owned, managed, > versioned, accessed, manipulated, etc. via the reservation service, > not by anything that happens to want reservation data.
Yeah this sums up my take on it too. - Colin
