Skip to content

MixedEmotions Architecture

Carlos Navarro edited this page Feb 22, 2017 · 1 revision

Architecture overview

Due to its Toolbox nature and the use of Docker container, modules from MixedEmotions can be added to a myriad of other architectures. However, MixedEmotions has been tested using a Mesos based architecture. Here is the full diagram of MixedEmotions architecture as a Platform.

MixedEmotions Architecture

The core of the architecture is a Mesos cluster deployed among several machines. Then Marathon is used to deploy and distribute the selected MixedEmotions' modules. Configuration examples have been provided in the marathon configurations. Then services can then be accessed using their REST interfaces and Mesos-DNS for retrieving their ip and ports.

The MixedEmotions' Orchestrator can be used as an example of how to use the MixedEmotions Platform. It can deal with either Docker services or external services, as long as they have a REST interface. It can be used as is or as a base for developing a new orchestrator.

The processing results could be persisted in an Elasticsearch cluster and then displayed in Kibi, a Kibana fork that adds Linked Data functionalities. For creating the Linked Data, MixedEmotions has a module designed for this.

The MixedEmotions Toolbox also has some modules for retrieving information from Twitter and Youtube. Those need a token to operate and will write outputs to disk.

Moreover, during the duration of the MixedEmotions project, some proprietary modules were developed alongside the rest of the platform. You can have more information about them in their wiki page

You can’t perform that action at this time.