Goodbye Microservices: From 100s of problem children to 1 superstar

Re:Goodbye Microservices: From 100s of problem children to 1... by foobarian on Tuesday July 10, 2018 @04:22PM (#17501769)

I hated that in our monolith Java web app, any random team could come along and pepper our team's module with global variable lookups and short term hacks that never get cleaned up. Even though we see the changes often times they are urgent changes needed right now, accompanied with promises to clean up later (which usually doesn't happen).

The nice thing about a SOA architecture is that it makes it harder to do this kind of cowboy programming. Yes maybe some quick business wins are harder than in a monolith, but I think (at least in our org) the cleaner architecture pays off by letting us move quicker on a different class of product projects since there is less technical debt.

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by p2t2p on Tuesday July 10, 2018 @05:04PM (#17502135)

I had enough of this stuff in my case so I locked repo down so only members of a team can merge PRs and no one can merge anything without a PR.

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by DCoder on Wednesday July 11, 2018 @01:29AM (#17504654)

Isn't that a technical solution to an organizational problem?

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by organsnyder on Wednesday July 11, 2018 @07:56AM (#17506182)

Yes. And that's okay, sometimes. To me, the difference is whether it's an organizational challenge or an organizational dysfunction. There will always be challenges inherent to operating a business—and technical solutions often play a critical part. However, if the issue is really an organizational malady that should be addressed, technical solutions probably aren't the right approach.

[ Parent | on HN ]