Microservices - shared microservice between two different projects

by 8bitjunkie   Last Updated June 12, 2019 00:05 AM

Organisation I work for has a single production namespace of microservices A, B, C, D, E, F, G.

Project 1 uses microservices A, B, C, D.

Project 2 uses microservices D, E, F, G.

Therefore Projects 1 and 2 have microservice D in common.

Project 1 wants to update microservice D and considers it part of its project.

Project 2 does not want to update microservice D and considers it part of its project.

I'm sure this is a common enterprise deployment problem but I am struggling to find the vocabulary to describe it.

Is this a deployment anti-pattern?

What is the best practice for this sort of problem?

Is it, for example, appropriate for microservice D to exist as two instances D1 and D2 in the namespace?



Related Questions


Updated October 07, 2018 21:05 PM

Updated October 08, 2018 18:05 PM

Updated May 10, 2018 22:05 PM

Updated March 02, 2017 10:05 AM