Overview on all »Convention« 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

A convention describes how a certain activity has to be done, like code or documentation conventions (e.g. always use JavaDoc when programming in Java, or stating the rule that each service needs a 1-paragraph summary in its documentation, etc.)

	Status	Title	Responsible	Deadline	Prio
1		Conventions for REST return codes and error handling	Mert Barutcu
2		Conventions for REST URIs	Tobi
3		What naming conventions should the services follow when communicating?	TimP
4		Time format for communication	Philipp Schmeier