Overview on all »API« Decisions

This is the architectural decision log for the Microservice Dungeon project. Download as CSV.

• All
   |   
• M
• S
• T
   |   
• API
• Convention
• DevOps
• Documentation
• Eventing
• Gameplay Rule
• Model
• Principle
• Quality Assurance
• Service Interaction
• Technology Stack

This aspect deals with all architectural decisions regarding API specification and implementation for synchronous communication (between clients and server, and between different services in the backend).

	Status	Title	Responsible	Deadline	Prio
1		APIs are specified in "API first" style	Stefan Bente
2		Asynchronous communication takes precedence over synchronous communication	Stefan Bente
3		Conventions for REST return codes and error handling	Mert Barutcu
4		Conventions for REST URIs	Tobi
5		What is the proper domain model for commands - who is owner?	Christopher Poloczek and Fabian Grüterich
6		AsyncAPI is used for specifying and documenting events	Tobi, Thomas Lang, and TimP
7		Tool for specifying REST APIs	Fabian Grüterich and nattyflo
8		UUIDs are to be used for IDs in APIs	Stefan Bente