Architecture

One Does Not Simply Make Architecture Decisions Alone

Vladas Diržys

Vladas Diržys

Vladas Diržys recently joined Autronica as Lead Cloud Architect, a global leader in fire and gas safety technology. In this role, he guides a distributed team in defining cloud architecture and best practices, focusing on building secure, scalable, and reliable AWS-based solutions for innovative safety systems.

With a background that includes 15 years of specialising in Live Data and serving as a Tribe Architect at Sportradar, Vladas maintains a strong interest in Domain-Driven Design, Event-Driven Architecture, Event Sourcing, Java, Kotlin, and modern cloud technologies.

1 / 2

Architecture is more than just diagrams. It is a set of important decisions. Many teams struggle with how to make these choices without a single "architect" becoming a bottleneck. This talk introduces the Architecture Advice Process. It is a simple way to let anyone make a decision as long as they seek advice from the right people. We will look at how to use Architecture Decision Records (ADRs) to document the "why" and keep everyone on the same page. Join me to learn how to give your team more autonomy while keeping your system's design clear and consistent.