Building Microservices with Go

Technical debt

If you have ever worked on a monolithic application, you are aware of the coupling and dependency that occurs between objects. This is predominately in the data layer; however, you also often find code that is not implementing correctly and is tightly bound to another object. Problems arise when you want to change this system; a change in one area has an undesired impact in another, and only one if you are lucky. An enormous effort happens in refactoring the system before changes are made. Often, what happens is that the modification is shoehorned into the existing code base without refactoring, and, to be brutally honest, it would be kinder to the system to take it outside, around the back of the barn, and unload two shotgun ...