Managing architectural decisions
A microservices architecture thrives when you allow teams to have autonomy. This doesn't mean that teams can do anything, but it gives them the freedom to make decisions under an umbrella of formally agreed principles. This is called shared governance, which states the consensus across the teams on how they want to address the broader architecture strategy for microservices.
The following aspects are important when evaluating this factor:
- Do you have shared governance in place?
- Are you maintaining an architecture journal along with your microservice to track decisions?
- Are your architecture journal documents all your architectural decisions?
- Is your architecture journal easily accessible by your team?
- Do you have a framework in place for evaluating tools, technologies, and frameworks?
