Core Platform Concepts

The core concepts of Monterosa / Interaction Cloud

Here, we'll give an overview of the core concepts, within Monterosa / Interaction Cloud, the infrastructure and key terms you'll need to know, before getting started.

The Platform's control interface is called Studio. This is where you'll create, schedule and manage all of your fan engagement activity.

FanKit is the React front-end toolkit that Monterosa apps and Experiences are built upon. It is the primary front-end framework used to power Monterosa Experiences.

Monterosa / Interaction Cloud is capable of handling huge volumes of data and EnMasse is the cloud mesh network of distributed processing powering the massive scalability of the system, allowing each app to connect via websocket.

Studio

Studio is the control interface for content creators and product teams. All devices are connected persistently to via socket connections, ready for content to be triggered.

Within Studio, every Organisation has their own dashboard where they can manage all of their fan engagement activity.

This is structured as follows:

  1. Spaces

  2. Projects

  3. Events

Below is some detail on how each concept works and is managed.

  1. Spaces

A Space is a container for multiple Projects. Spaces group Projects together and allow you to manage them all in one place.

By having multiple Projects within one space, you can manage all styling settings at Space level, meaning that any branding can be consistent across all Projects within that Space, without needing to set up every time.

This can be configured in Space Settings.

  1. Projects

A Project is a container for an Experience. Every Project is associated with an App and within your Projects is where you will manage your Events.

  1. Events

The Platform is built around the concept of Events that you will create to align with your content calendar: an event can be a campaign, a game, a show, or any duration of time you choose. You can create, schedule, manage and close an event from within the Platform.Studio infrastructure

Studio infrastructure

The infrastructure is a distributed series of edge nodes typically running on AWS which handle the core socket connectivity. There are layers of control and dependency, with a standard approach to fail-overs if and when a server has a problem, the client device will simply connect to another and state is preserved.

Processing, for example counting the number of votes cast or the percentage of people who have predicted an outcome, takes place in a distributed manner, ensuring high levels of scalability.

The infrastructure uses a lightweight proprietary protocol that is available in either plain text or via secure web sockets. The underlying edge servers, known as the EnMasse Mesh, are cloned instances which have awareness of each other. They are written in C++ for speed and efficiency, fine tuned and fully supported by our team.

The platform does not rely on third party data transport providers or intermediaries.

FanKit

FanKit powers real-time web apps designed for interactive audience engagement use cases. It is the primary front-end framework used to power Monterosa Experiences.

It is a responsive web app built with React, designed to be integrated into existing websites and native apps. It features a range of real-time interactive Elements, the building blocks of each Experience.

EnMasse Mesh

Under the hood, the Interaction Cloud uses a proprietary, replicable mesh architecture created by Monterosa and running on Amazon Web Services. It provides unparalleled scale and failure tolerance:

  • Instant publishing

  • Minimal latency

  • No caching of live content

  • CDN serves only assets

  • Rapid fail-over if AWS instance dies

Last updated

Was this helpful?