Hi Israel, just one question maybe you can clarify things for me. You said each microservices should have its own DB but my question is, if we can restrict some API's to certain tables in the same DM wouldn't that achieve the same purpose? In that way each time may have it's own access in same DBspace.
i think if you feel the need to still possibly share a db but separate by table maybe some of the microservices could be combined? so u can truly keep them independent, i just believe if u share a db but separate by table that still introduces issues in the future if the tables need to be changed, relationships updated, even if a table doesn't use it, adds more checks to everything so while i see what you are saying it seems a bit risky and maybe means you should take a second look at the microservices and how they are divided what do u think?
How do you guys decide on what Architecture to use?
Hi Israel, just one question maybe you can clarify things for me. You said each microservices should have its own DB but my question is, if we can restrict some API's to certain tables in the same DM wouldn't that achieve the same purpose? In that way each time may have it's own access in same DBspace.
i think if you feel the need to still possibly share a db but separate by table maybe some of the microservices could be combined? so u can truly keep them independent, i just believe if u share a db but separate by table that still introduces issues in the future if the tables need to be changed, relationships updated, even if a table doesn't use it, adds more checks to everything
so while i see what you are saying it seems a bit risky and maybe means you should take a second look at the microservices and how they are divided
what do u think?