Domain
The domain is responsible for common functions such as service registry, security services, failover management (Grid) and the action repository. There is typically 1 domain running at a time although it supports a passive failover instance.
CEP Server
The CEP Server is the working node in the meshIQ platform. Much like an application server, it provides a set of facilities that are used by the services that make up the meshIQ platform. The may be only 1 but more often there are several CEP Servers. They can also be run with as a primary and a secondary using an active/active model (Grid).
Services
Services provide the functionality that make up the meshIQ platform. There are core services, data services, scheduler, management and tracking services. Multiple services can share a CEP Server, or they can be spread across several to increase scalability.
Data Collectors
Each component consumes data from the managed environment. These collectors interact with the managed systems using their application programing interfaces and publish it to the meshIQ platform services.
Application Server
In order to host the web facing applications, an application server is required. This can be Tomcat, which is shipped with the product, or any other application server.
Database
In order to store persistent data, a SQL based database is required. A PostgreSQL instance is included with prebuilt distributions which is typically replaced with a database instance managed by a core services team.
Solr Cloud
For storage of high volume data, a Solr Cloud configuration is required. With 1 node, this can be used to store configuration and basic information. For most scenarios, it is typical to have at least 3 data nodes.
Other Components
Depending on services in use, there are some additional components that may be used. These include Kafka, zookeeper, activeMQ, and PostgreSQL.
Example Architecture
The following diagram shows a typical meshIQ platform deployment. This would typically be multiple servers running virtualized or using containers. Note that all components shown interact with each other using secure protocols.