Designing the infrastructure architecture
At this point, we’ve pitched our proposal. Once we get the initial buy-in from all teams and executive sponsors involved, it’s time to move to the next stage: we need to think about designing the solution and how it fits with the underlying infrastructure to achieve all those non-functional requirements of our organization: resiliency, availability, auditability, security, mandatory integrations, and so on.
While we must not over-engineer from the start, it’s important to be aware of all the requirements that will have an impact on our infrastructure decisions. Here are a couple of questions we need to be able to answer:
- How, who, and where are we deploying, updating, and operating the platform?
- Are there organizational requirements to run on certain infrastructure?
- Is there a requirement to run our solution across multiple geographical regions or even across multiple infrastructure providers?
- Are...
