Architecture Governance

Alexander Polomodov and Pavel Lakosnikov discuss architecture governance in large companies. Pavel's path from game development and a high-load product to Avito shows how engineering perspective changes with the system. Architecture means decisions that shape the cost and freedom of future change.

Avito's architecture function grew out of reliability and incident work. The conversation separates technical from product reliability, internal quality from external signals. At scale, an architect cannot fix everything personally; influence comes through adoption, tooling, and repeatable processes.

Architecture governance and platform engineering operate side by side but own different layers. Verifiable rules can become tooling, while a complex decision needs consultation, early design review, and a justified exception. A team needs context before implementation becomes expensive, not at a final gate.

Architecture metrics are useful and dangerous. Coupling, cohesion, leaking abstractions, and fitness functions connect the system with observable signals, yet invite local optimization. Governance impact is better discussed through outcomes and engineering goals. The finale moves from services to domains and broad engineering expertise.