Software architecture requires balance. During the 20 years I’ve been leading technology organizations to build products, mostly via Agile, I’ve learned some rules that have helped me — and my teams — successfully strike the right balance. These aren’t technically focused rules; they’re more generic, so they apply to monolithic, layered, service-oriented, and microservice architectures equally well. One of these rules is the subject of this Advisor.
Not a member? Gain Access to the Cutter Experts today — register now to read select open-access articles.
Member/Guest loginForgot your password?