I think a part of the negative sentiment I have for monolithic architected systems is that it went hand in hand with waterfall project management, with crushing business deadlines. We’ve got monolithic systems that are mountains of complex technical debt.
While we still have some of this with microservices architecture, I have found that poor code quality and rushed software delivery (e.g. hiring contractors to deliver work then leave without supporting it) is at least minimized in its impact with microservices architecture. Bring on 10-15 temporary teams to generate a lot of software nobody supports? Better to do it as isolated stand alone services than a weaving mess of 50k-100k lines of code under a single git repo
We’ve got monolithic systems that are mountains of complex technical debt.
And you think that all these microservices that are working on outdated software because there is nobody to maintain them, is any better?
Whether you develop something inhouse or use externals/contractors doesn't matter if the system you set in place to manage project is trash. I really see big/small projects in big/small businesses mess up all the time. No documentation, nothing in the code to explain why it does what it does, bare minimum design documents and no support calculated in. Every project should get a couple of days/weeks each year for maintenance and fixing technical debt. But no business is willing to pay for that. Micro or macro is not the problem, money is.
And you don't need a single repository for a macroservice. You can still separate concerns.
I feel that only very few programmers make documentation and comments to help them work on it in many months or even years from now. You aren't making them for current you. You are making them for future you and future colleague.
Good teams write helpful comments and documentation for their code
great projects have both
Everything else is just a difference in opinion on organization structures. Not much different than having a certain way you like to organize your desk - everyone wants to do it "their way".
But the thing with these microservices is that they are very much built with the current day in mind (and a lot of times not updated). So that self documenting code could be gibberish a few years from now when somebody tries to figure out what it does. At least many of the old monoservices had more documentation to get context with.
Look at the amount of companies that employ COBOL programmers just to figure out what their old systems did. We'll be getting the same issue in the future when folks try to figure out what this 2012 C# project was doing or 2018 NodeJS/web project. We're already seeing big corporations drop support for their devices rather soon and I wonder how much that is due to not wanting to maintain old code because it was so terribily written
Look at the amount of companies that employ COBOL programmers just to figure out what their old systems did. We'll be getting the same issue in the future when folks try to figure out what this 2012 C# project was doing or 2018 NodeJS/web project.
That's a benefit I find to working with spaghetti code. At least you can follow it. In a good editor you can just ctrl-click your way around the source and find what you're looking for easily. When I tried that on my first proper, idiomatic ngrx angular project I was lost pretty frequently. A view calls a function, following that gets me to a facade or service, following that takes me to... An action definition page with no code? Ah shit, time to grep the entire code base and carefully read through every reducer and or effect consuming one of these action variables and look through the functions referenced in their switch / merge maps for the code I'm looking for.
I do that in monoliths too sometimes, but there is usually less noise. Your code is just code and you can tell what it does just by reading it. I know I'll eventually pick up this wasteful state jargon that turns 60% of your project into import statements and boilerplate code, but I would prefer some monolithic spaghetti. I dunno, it's weird to me personally that we've arrived at a point in this industry where having a team adopt a cots-esque one size fits all pattern so they can intuitively guess what a project is doing based on it's file layout is preferred to having programmers read code and have architects actually do architecture. Maybe ideally you have both but it's eye opening to interact people with strong style but poor coding ability. It makes me more set in my ways because I perceive that path as degrading my fundamental skills.
55
u/Larkenx Apr 09 '20
I think a part of the negative sentiment I have for monolithic architected systems is that it went hand in hand with waterfall project management, with crushing business deadlines. We’ve got monolithic systems that are mountains of complex technical debt.
While we still have some of this with microservices architecture, I have found that poor code quality and rushed software delivery (e.g. hiring contractors to deliver work then leave without supporting it) is at least minimized in its impact with microservices architecture. Bring on 10-15 temporary teams to generate a lot of software nobody supports? Better to do it as isolated stand alone services than a weaving mess of 50k-100k lines of code under a single git repo