Our code base consisted of multiple compiled languages, so we weren’t able to use any of the standard open-source dependency management tools out there. Most of these were intended to use with one particular language (e.g. Java only, or Perl only, or C# only), so we rolled our own.
We’ll Never Know Whether Monorepos Are Better
Dan Fabulich
946

This is really confusing to me. What does splitting to multi repo have to do with this? Did the split make you have multi language? Whether it was mono or multi, wouldn’t you still have this issue?

Regardless, why didn’t you take the dependency and stand it up as a service with an API. Then any other service could call it to use it. You wouldn’t need to have Java code use Perl code. You would have Java code call an API. The fact that the endpoint was written in Perl would be an implementation detail.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.