> For the complete documentation index, see [llms.txt](https://docs.eventoframework.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventoframework.com/getting-started/todolist-recq-tutorial/recq-payload-evento-implementation.md).

# RECQ Payload Evento Implementation

Once we've defined all our payloads or "message types" we need to implement them using Evento Framework creating a Class for each Payload and adding required fields to handle those messages properly.

* Domain Command
* Domain Events
* Queries
* Views

{% hint style="info" %}
As a best practice, we suggest storing all Payloads inside a common library inside a package called "API" like: `com.eventoframework.demo.todo.api`

Then device payloads by domain and then by type following this sample scaffolding:

```
├───user
│   ├───command
│   ├───event
│   ├───query
│   ├───view
│   └───enum
└───todo
    ├───command
    ├───event
    ├───query
    ├───view
    └───enum
```

{% endhint %}