# Building evolutionary architectures

## Pitch

**Support Constant Change**

The software development ecosystem is constantly changing, providing a constant stream of new tools, frameworks, techniques, and paradigms. 

Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. 

This practical guide ties those parts together with a new way to think about architecture and time.

![](/files/-MBikfbB7GFLLjdqTWMw)

## Notes

### Evolutionary architecture

* Other possible names ?
  * Agile
  * Incremental
  * Continual
  * ...
* Incremental and Guided
  * Some objective exists Move towards

### Fitness functions 

* From genetic algorithm to define success
* "An architectural fitness function provides an objective integrity assessment of some characteristics"
* System wide fitness function
  * Collection of fitness functions
    * Architecture metrics
    * Integrations tests
    * Unit tests
    * Contract Tests
    * Monitors
    * ... 
* Categories
  * Atomic
    * Run against a singular context
    * Exercise 1 particular aspect
    * Unit test for example
  * Holistic
    * Shared context
  * Triggered
  * Continual

## Mind map

![](/files/-MBin57Njf5r1SGeI3kO)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://yoan-thirion.gitbook.io/knowledge-base/xtrem-reading/resources/book-notes/building-evolutionary-architectures.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.