Question C-9-4: How can we handle a 'large number' of architecture decisions?

#decision

Create a blog (RSS-feed) and write a brief entry for your important decisions. Tag those with labels (e.g.: frontend, backend, SAP-interface or similar), so stakeholders can filter them.

Such a blog shows the history of your system quite well. You can combine the blog with the idea of architecture decision records (see question C-9-3).

arc42 offers architecture training.

The data is currently loaded from the backend and should display here shortly. If not, you can see the next dates at trainings.arc42.org .