API Specification for Team "Variants"

Acronym

team-variants-api-spec

Belongs to

Team Variants

Responsible

Duzun und akosmehl

History

(v1)   2021-02-05 - created initially

(v2)   2021-02-11 - added resolution and reason of the resolution

Why is there need for such a decision?

There needs to be a synchronous, REST-based API for communication with the UI.

Additional sources for better understanding the background

• Bente: Inhaltsimpuls zu “Was sind Aggregate”
• Bente, Vorlesungsmitschnitte ST2 (Achtung, nicht nachbearbeitet)
  • Aggregates, Teil 1
  • Aggregates, Teil 2
• Bente: Inhaltsimpuls zu Grundlagen von REST
• Bente, Vorlesungsmitschnitte ST2 (Achtung, nicht nachbearbeitet)
  • Grundlagen von REST
  • Standards und Regeln bei REST
  • Coding REST Level 2 mit Spring Web MVC, Teil 1
  • Coding REST Level 2 mit Spring Web MVC, Teil 2
  • Coding REST Level 2 mit Spring Web MVC, Teil 3
  • REST Level 3
  • Coding REST Level 3, Happy Path
  • Coding REST Level 3, Sonderfälle
• Levin, G. (2017, March 25). Internal vs. External APIs. REST API and Beyond

Viable Options

n/a

Alternatives not seriously considered

n/a

How is this decision evaluated?

• Result should be presented in the plenum
• UID as stakeholder needs to be able to comment (Hr. Nguyen)

Resolution Details

The Resolution of the Variant API-Specification can be found in the wiki.

Reasons for the resolution

Detailed Reasons for this resolution of the Variant API-Specification can be found in the wiki.