In software projects, it's important to write down why we make certain big decisions about how the software is built. These written records are called Architecture Decision Records (ADRs). They help us remember why we made these choices, especially when new team members join or when we need to make future decisions. This talk will introduce ADRs and explain why they are so useful. We will cover what ADRs are, why we need them, and how they help teams work better together. This is great for anyone who wants to keep track of important decisions in a simple and organized way. Join me to learn how ADRs can make your software projects smoother and more successful.
Vladas Diržys
Autronica Fire and Security AS
Vladas Diržys recently joined Autronica Fire and Security AS 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 specializing 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, including AWS, Kubernetes, Terraform, and CI/CD.