yester is part of a bigger application which aims at automating the curriculum development. In the overall implementation we adopted the micro service architectural style. yester is the micro service that manages all resources accessed during the curriculum development.

The key functionalities offered by yester include:

• user management

The early design of the micro service should include a communication management component (message consumer and message producer); a database management component (offering an API to manipulate RethinkDB)

Before going any further one needs to take a closer look at the following points

Note1: one needs to be careful how the concurrency is managed here. Note2: I need to design more carefully how many actors should be created for the management of the communicators (consumer and producer) and the db management API implementation Note3: Need to identify what are the different types of messages that one should expect during the message consumption and production. Also the same need might apply for the DB API.