Architecture as Code: Quantifying Architectural Trade offs by Neal Ford

Video Description

Architects often describe their work in diagrams and other visual artifacts, but how can they test to see if the implementation is aligned with the architecture? Architects are expected to not only design new systems, but continuously govern what they’ve already built and ensure that their architecture is aligned with the technical and business environment. This session uncovers a new way to think about architecture—as code. We have infrastructure, policy, data, and a host of other things “as code”, but not architecture…until now. This course covers numerous intersections of software architecture with all the tendrils of the organization, defining each intersection using code. This session provides an overview of the architectural intersections with implementation, infrastructure, engineering practices, team topologies, data topologies, systems integration, the enterprise, and the business environment , defining each interaction with fitness functions that allow architects to not only design solutions but make sure they are implemented and aligned correctly via automated verification. This isn't a testing framework, it's a feedback framework.