Have you ever asked yourself, how you should design an API - REST or Event — you won't hate to use? The project tries to bring you the process how to define an API you would love to use step by step. We assume that the API is defined in an API-First approach. That means, we will define the API and only afterward we will implement client and server or for events consumer and producer.

The entire process is explained, using an example, which shouldn't be too easy, but which shouldn't be too complex as well. The example is a task management system. The DDD process with Domain Story Telling and Event Storming is already done.

1. Exercise 1 Discussion of the necessary data exchange using a context map out of a DDD process.
2. Exercise 2 Create a consumer-driven API for the necessary Document Management System.
3. Exercise 3 Define Properties for the Objects