Base Architecture

The eva platform is based on a microservices architecture and every component has its Rest APIs. A basic understanding of this architecture will help understand the APIs and explanations on the following chapter. For that, consider the diagram below.

The Broker is the orchestrator of the solution. It is responsible for receiving the information needed for executing a conversation. Its API is the one called when a channel receives a message from the user. Also, it is responsible for calling NLPs dynamically, depending on which NLP was selected by the user in the Cockpit, and for calling external services when these are registered in the Cockpit through the webhook fields.

The main database, which is used by the Broker, is a MySQL database that contains all configuration made through the Cockpit as well as data generated through conversations by the Broker.

Besides the Broker, that orchestrates the call between the microservices, another important component is the Dialog Manager, responsible for managing and executing the virtual agent conversation flow. This module has its own NoSQL database, for a virtual agent optimal performance.

All conversation flows created through the Cockpit are stored in this MongoDB.

The extraction details explained in the following chapters will details only the MySQL database, since it is that contains the conversation logs.