gamesterdude

From a proper architecture perspective, service B should never directly connect to service A database. Going through API layer gives a little bit of abastraction but still not the best. A question to ask, if both projects need those tables, why not keep it as one project in project A? You can just put project B tables in a new schema for logical separation.