Designing relations in Microservices architecture
I am new in microservices architecture and I am a bit confused about designing relations between data of each Microservice. So I think about design as its on picture bellow:
So my question is:
Is it good to create separate relations service that will connect id of documents or maybe there is another way to solve it?
You seem to be under the impression that microservices are the application layer over the data layer, and so, you need to slap microservices on individual database tables.
But, microservices are implementation of domain driven design. Each microservice implements a subdomain or bounded context or an aggregate, so that there is less dependency between microservices, and each team can work mostly independently on features.
In the design you mentioned, depending upon the use-cases, building to user assignment could belong to user aggregate (users service) or building aggregate (building service). For an excellent blog on what aggregates are, check out What are aggregates.
- Math.Sin() gives incorrect value
- How to run my python script when the sunOS is start booting
- Express-session: not resetting cookie expiration on each request
- Getting a stack overflow exception when normalizing a vector
- Edit default summary function in R gives error for multiple variables
- What was a For loop? Why isn't it needed in R?
- How to use download button in shiny and save results in various formats (csv, texte, pdf, spss...)?
- Why are there two assignment operators, `<-` and `->` in R?
- lm()$assign: what is it?
- How to get the value of list(...) in R and S functions
- Design matrix for MLM from library(lme4) with fixed and random effects
- how to generate elements not included in my sample
- Create a matrix with gradually changing values without a for loop
- Emacs ESS and S-plus ( S+ ) 8.1 compatability
- How to lag date-index in a time-series in R?
- Nonlinear regression in R / S
- Calling R from S-Plus?