The Death of Microservice Madness in 2018

Re:The Death of Microservice Madness in 2018 by eadmund on Sunday January 21, 2018 @10:03PM (#16201571)

> 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.

[ Parent | on HN ]

Re:The Death of Microservice Madness in 2018 by paulddraper on Sunday January 21, 2018 @11:28PM (#16201932)

Agreed. Multiple closely dependent repos by one organization is the real nightmare.

[ Parent | on HN ]

Re:The Death of Microservice Madness in 2018 by crescentfresh on Monday January 22, 2018 @11:06AM (#16205405)

> 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.

[ Parent | on HN ]

Re:The Death of Microservice Madness in 2018 by eadmund on Tuesday January 23, 2018 @08:45PM (#16219671)

> 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.

[ Parent | on HN ]