Re:Analysis of Software Architectures
by kisstheblade on Saturday January 09, 2016 @04:24PM
(#10872944)
Agreed.
Usually it's always the "user" object which cuts across services. Was wondering if there is some common pattern for handling this.
For the scenario I outlined here some kind of "third service" / aggregated view of the data could also be a solution. Ie. store the data needed for queries in some queryable datastore (nosql, sql; pull the info from the needed services and refresh the view when needed)
Usually it's always the "user" object which cuts across services. Was wondering if there is some common pattern for handling this.
For the scenario I outlined here some kind of "third service" / aggregated view of the data could also be a solution. Ie. store the data needed for queries in some queryable datastore (nosql, sql; pull the info from the needed services and refresh the view when needed)