The big enterprise in which I work wants to mandate which we have to write a microservice for each individual HTTP endpoint, since we cannot even have an artifactory for code sharing the code duplication is going off the charts and having these microservices sharing a single DB we are creating a big and messy distributed monolith.

Artifactory for JAR management?

@IntrusionCM Our IT management doesn't want to give it to us so we have to resort to very ugly things such as emailing JARs around or worse, including a whole microservice inside another as JAR.

If you're including one microservice inside another as a jar, then... well, I don't know what that is, but it sure as hell ain't a microservice.

Is this a suit with 0 programming knowledge mandating these decisions because he saw a video on YouTube or something?

@AlmondSauce he said sharing the code duplication.

Libraries / Frameworks / Common code cannot be shared via an versioned JAR as artifactory / registry is missing.

Makes sense?

It makes sense conceptually, but it's nuts. By all means extract common code and shove it in a repository that you reference from elsewhere, but not the entire microservice as a hard coded jar. I'd prefer code duplication than that nonsense.

If you work somewhere that refuses to give you the basic tools needed to do your job, it's not a great sign.

@AlmondSauce it isn’t possible to do that since it would break the CI pipelines

@DEVil666 How would putting common code in a repository break a CI pipeline?!

@AlmondSauce our pipelines cannot “see” external Git repositories but only the repository in which the micro service code is stored

@DEVil666 sounds like "idiots inside" TM.