> For the complete documentation index, see [llms.txt](https://amartyushov.gitbook.io/tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amartyushov.gitbook.io/tech/app-aspects/software-architecture.md).

# Software architecture

## [TOGAF](https://www.opengroup.org/togaf/10thedition)

TOGAF is a standardisation of the architecture. High level definition of principal. 

Looks **too top level** and not applicable for development. Can be **useful for writing technical documents when it is necessary to describe Rationale, Implications, Strategies.**

## Managing Shared Database Changes  

[Lesson 136](https://developertoarchitect.com/lessons/lesson136.html)

**Problem description**: Multiple services share the same DB. If you store all entities in one lib => any change in the db schema will require update of all services. It may introduce inconsistency in representation layer (versioning of this entities.jar does not help). 

**Solution**: Introduce a logical db partitioning. It means split entities by some boundaries so that services depends only on parts of these entities. It will mean that not every change in schema will require update of ALL services.

![](/files/8GO9OAKcwSU7XdngN8kV)

## Messaging

### Preventing data loss

![](/files/ttol2hC9K90eH6dPZpn3)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://amartyushov.gitbook.io/tech/app-aspects/software-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.