Architecture is code, which is an idea of architecture design and governance. It revolves around a series of architecture patterns, combines and presents architecture elements and features, and closely integrates architecture decisions and design principles with the system.
For example, in my last article, ” Modeling “Architecture”: How to Describe Software Architecture in Code? As mentioned in the book, it is quite difficult to accurately describe the architecture of software. At the implementation level alone, it’s hard to get everyone to agree on a standard model, “Oh, this is the architecture”. Therefore, when the architecture cannot be defined, it is difficult to give an architecture governance model that convinces everyone. After all: Models are only right, never right .
However, we (ArchGuard Team) will still build an architecture model and an architecture governance model in ArchGuard as a recommended ” best practice “. In addition to this, we should also provide a possibility to customize the enterprise application architecture, which is architecture as code . For junior architects, they only need to implement ArchGuard’s best practices; for intermediate and senior architects, they can build their own architecture system based on the plug-in capabilities + DSL provided by ArchGuard.
So, as you’ve seen in other systems, to provide this capability requires a certain amount of coding, configuration, etc. Therefore, we need to build an architecture-as-code system. So, the question is, what the hell is code.
What is Architecture as Code?
Original article: Architecture as Code: Coding Next-Generation Enterprise (Application) Architecture Systems
For more exciting content, welcome to search and follow my WeChat public account: Phodal
This article is reprinted from: http://www.phodal.com/blog/architecture-as-code/
This site is for inclusion only, and the copyright belongs to the original author.