3 ms·
> They developed 12 seperate applications, all in the same repo, deployed independently it's own JVM. I've dealt with an even worse system, with a dozen separa
by eadmund 9y ago
> They developed 12 seperate applications, all in the same repo, deployed independently it's own JVM.
I've dealt with an even worse system, with a dozen separate applications, each in its own repo, then with various repos containing shared code. But the whole thing was really one interconnected system, such that a change to one component often required changes to the shared code, which required updates to all the other services.
It was a nightmare. At least your folks had the good sense to use a single repository.
- paulddraper 9y agoAgreed. Multiple closely dependent repos by one organization is the real nightmare.
- crescentfresh 9y ago> then with various repos containing shared code What source control system? Also, from the article: > even though theoretically services can be deployed in isolation, you find that due to the inter-dependencies between services, you have to deploy sets of services as a group This is the situation we are in, like you were.
- eadmund 9y ago> What source control system? Git in our case. And our direction was not to use submodules or anything like that to make life manageable. It was pretty unpleasant.