Yesterday’s post spoke of how the accumulation of features was limiting us to small, incremental change.
The diagram below re-tells that story:
You’ve probably noticed that microservices are the big buzz in our industry. They’re perceived as being the big white hope for our future. I have my reservations though.
If you’re at t0 in the chart above, microservices allow for rapid rollout of features, whole small-grid architectures even (in a Lean / MVP world). My reservations stem from the propensity for rapid release of microservices to amplify the accumulation of tech debt (ie the escalation of maintenance and testing in the chart above). They have the potential to take organisations to t0+100 really quickly.
The upside though is that replacement or re-factoring of smaller modules (ie microservices) should be easier than the change-out of monolithic software suites. The one caveat… we have to commit to a culture of subtraction projects being as important as feature releases.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email