Minimum Viable Architecture

Many projects start with much excitement in architecting the perfect solution for the problem that will solve all non-functional requirements now and in the future. How can we avoid overengineering and deliver the first release faster? Ideally in a way that allows us to iterate and improve the system design as we learn more about the problem.

In this talk, I will share our experiences in building digital services for Finland's largest hotel chain. The main focus will be on the hotel reservation website. We will cover how architectural decisions affected our velocity and how we applied these learnings in newer iterations.

Martin has been building software for over 15 years from 3D game engines to distributed databases. His current focus is responsible e-commerce. When not on a computer, you'll find him exploring the archipelago by boat or stumbling on ski trails depending on the weather.