SIG APIs

The SIG discusses all architectural decisions regarding synchronous communication (between client and server, and between different server modules).

Team members:

1. jalue (also member of team Requirements)
2. FalahSama (also member of team Analysis)
3. SohleDelfin6504 (also member of team Requirements)
4. TheBuro (also member of team Requirements)

Status	Title	Responsible	Deadline
	Conventions for REST return codes and error handling	jalue
	Conventions for REST URIs	Stefan Bente
	A DTO pattern should be used in the APIs	Stefan Bente
	UUIDs are to be used for Entity IDs (PKs and API IDs)	Stefan Bente
	The preferred way of synchronous communication between modules are api calls	jalue
	In the backend, Spring is used as predominant programming framework	Stefan Bente
	In the backend, Java is used as programming language	Stefan Bente
	JSON	jalue und SohleDelfin6504
	Relational database vs. NO-SQL DB	TheBuro und FalahSama
	Access security through REST-API authentication methods	TheBuro
	Configuration database state dev and prod	TheBuro und FalahSama
	MYSQL used as database	TheBuro und FalahSama
	Database version control	TheBuro und FalahSama
	API-Documentation is done using Swagger	FalahSama
	Web MVC with manual link	SohleDelfin6504
	API Style is REST Level 3	jalue und SohleDelfin6504
	The Uri style is lower camel case	jalue