(v7) Microservices Architecture

Microservices Architecture

The Composer platform is architected as a set of loosely-coupled Java microservices. Unlike traditional business intelligence software, which is deployed as a monolithic application, a microservices architecture allows for the following benefits:

• Faster deployment of new functionality
• Optimal resource management
• Faster recovery in some failure scenarios
• Greater deployment flexibility

Each Composer microservice runs in its own Java Virtual Machine (JVM) to optimize memory allocation and runtime attributes to meet its function and load. A failure in one microservice does not take down all Composer, and recovery is faster because only the failed microservice needs to restart. Deploying new functionality, such as an updated or custom data store connector, occurs by auto-discovery, and without requiring a server restart.

Separately, Composer centralizes its metadata store in a relational database and includes an internal messaging queue. The communication protocols used by the microservices include WebSockets (for real-time bidirectional communication) and HTTP/S.

For more information about individual microservices, see:

• Composer server microservice for its Web-Based User Interface
• Query Engine Microservice
• Data Connector Microservices
• Data Writer Microservice
• Service Monitor Microservice
• Configuration Microservice
• Service Discovery Microservice
• Screenshot Microservice
• Tracing Microservice

The following links provide general information about all Composer microservices:

• Composer Microservice Name Reference
• Composer Microservice Startup Order
• Start Composer Microservices
• Stop Composer Microservices
• Restart Composer Microservices
• Scaling Composer Microservices
• Manage Composer v7 Microservices Using the Command Line Utility
• Composer System Metrics