#51 Evolutionary Architecture: From Articles to Videos
From simplicity to maintainability. From maintainability to complexity. From complexity to growth. Evolutionary architecture will help you to stay focused on the most important things at a given time.
Last December, I wrote articles about evolutionary architecture. If you observe me for a longer time, you know that this is one of my favorite topics. Here you can find the first one in the series:
Today, I would like to share videos covering the same content.
Why is this topic so important to me? In general, I am lazy. I don't want unnecessary complexity when building projects. That is why I am skeptical of microservices, Redis, Kafka, and similar unless absolutely needed.
However, the world isn't black and white. Sometimes they are a perfect fit. But in my experience (30 direct projects, dozens of consulting gigs), they were truly justified around three times.
The videos dive into the same principles of keeping architecture simple, flexible, and focused on actual business needs rather than technical hype. You will get extended and practical insights on how to deal with complexity and how to focus on maintainability - all delivered in a format that might be easier to consume during your commute or coffee break.
If you found value in the written series, you will probably enjoy this alternative take on the same ideas. And if you are new to the concept of evolutionary architecture, either format will help you avoid the common pitfall of overengineering your next project.
How Did I Start Building Successful Apps - Evolutionary Architecture #1
In this video, I describe how I approach building successful apps by leveraging evolutionary architecture - a concept that grows and extends within time in your application.
How Did I Start To Focus On Simplicity In My Apps - Evolutionary Architecture #2
In this step - Simplicity - we are not reinventing the wheel. The goal is dead simple: build the most straightforward solution that works right now.
How Do You Keep Your Apps Maintainable - Evolutionary Architecture #3
At some point, we need to think about another aspect of our system - like how easy it is to maintain.
How Do I React To The Growth of My Apps? Evolutionary Architecture #4
At some point, you need to react to your app's growth. The number of users, requests, several development teams, and frequency of changes are common factors that help you decide whether to extract part of your application to microservices or wait a bit longer.
In this video, you will learn about four common decision factors that will help you. Make sure that you check them before deciding on microservices.
Hungry for more? Ready to see these principles in action? Check out my comprehensive 400-page book that walks through real-world applications. Grab it now with a 25% discount – offer valid only until the end of next week!