# 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.

![](https://415484505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LxtoAXZwwOc4XGto8vb%2Fuploads%2FLn0ud8MizEc0md49I1nK%2FScreenshot%202022-04-25%20at%2008.46.59.png?alt=media\&token=920ce1aa-a92b-4a3c-8002-1bfb99185dc8)

## Messaging

### Preventing data loss

![](https://415484505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LxtoAXZwwOc4XGto8vb%2Fuploads%2F8YiVcDM5vVFpaMNDu0VN%2FScreenshot%202022-04-28%20at%2009.08.48.png?alt=media\&token=5b87a916-2ea8-45b9-8666-a46a45132403)