Software
Microservices and Monoliths
One thing I've had to do a lot over the years is deal with a Monolith . In some cases, it was not a bad experience; in others, it was pretty horrific. Often, monoliths aren't an intended outcome, but unless you take explicit actions to isolate functionality as the code grows, the code base will gradually grow into a Ball of Mud. A codebase starts out small and focused, but over time it grows organically as new user stories are added. As these new user stories
By Arthur Correa • 0 Comments
Continue Reading