Cloud architectures are complex systems with many moving parts and numerous stakeholders. While a clear roadmap and strategy can help keep your infrastructure organized, without a dedicated governing body to take ownership of the system and all its processes as a whole, it will be difficult (if not impossible) to keep your cloud operations aligned
An Architecture Compliance review is a scrutiny of the compliance of a specific project against established architectural criteria, spirit, and business objectives. A formal process for such reviews normally forms the core of an Enterprise Architecture Compliance strategy. Purpose The goals of an Architecture Compliance review include some or all of the following: First and
A key relationship between the architecture and the implementation lies in the definitions of the terms “conformant”, “compliant”, etc. While terminology usage may differ between organizations, the concepts of levels of conformance illustrated below should prove useful in formulating an IT compliance strategy. Irrelevant The implementation has no features in common with the architecture specification
The microservices era has been good for software architecture. I remember when the idea of multiple databases was punishable by death. But, the over-focus on micro has detracted from the true benefits of microservices which are about improving the quality and speed of development. Over the past couple of years, I’ve seen organizations referring to microservices as Domain
Design patterns are part of the day to day of any software developer, whether they realize it or not. In this article, we will look at how to identify these patterns out in the wild and look at how you can start using them in your own projects. What are design patterns? Design patterns, simply