Architecture tests check that software keeps in full compliance of architecture decisions (or ADRs) after code changes were committed.
Here I propose Continuous Change, a new methodology for creating software with only one foundational pillar: never stop challenging our code, never stop changing our software..
According to their fundamental different features, master entities and transaction entities are defined, and a different location in the layers of an hexagonal architecture is proposed.
I consider the aversion to change that monoliths exhibit as their defining feature. And the benefits of embracing change in organizations based on software are explored.
In this episode V in the review series of the GSAS 2019 in Barcelona, we learn what is software architecture thanks to a master class given by Mark Richards, and review two more debates.
In this episode IV in the review series of the GSAS 2019 in Barcelona, we learn more about reactive architectures, asynchronicity, and complexity.
In this episode III in the review series of the GSAS 2019 in Barcelona, we revisit the monolith versus microservices debate again, and introduce the outstanding concept of continuous change.
A review of my attendance to the Global Software Architecture Summit which took place in Barcelona this 10th of October, 2019.
In this episode II in the review series of the GSAS 2019 in Barcelona, we learned about complexity, observability, and the neverending discussion monolith vs microservices.
In this episode I in the review series of the GSAS 2019 in Barcelona, we see code repositories as theory representations, and as knowledge repositories as well.