Conductor Architecture

Conductor Manager comprises the following main parts:

• Conductor Manager
• Conductor Management Console

Conductor Manager

Conductor Manager consists of the Studio Conductor code and a set of open-source applications. For an in depth explanation of these applications, click here.

The Conductor Manager architecture is designed to support all potential operational workflows you might require when managing your applications, including:

• Event-stream processing
• Processing secured requests
• Metrics queueing, aggregation and analysis
• Logs/events queueing, aggregation and analysis
• Manual or automated task execution and queueing, based on live streams of events or aggregated data
• Interaction with Conductor Agent, for executing tasks on, and maintaining, application hosts

You can also communicate with Conductor Manager using the command-line interface, which uses the Studio Conductor REST client module to interact with the Studio Conductor REST service.

All requests are served via a proxy.

Conductor Management Console

Studio Conductor includes a Conductor Management Console that provides the same features as the CLI, as well as others. For more information, click here.

Security

Security involves managing communication with the Conductor Manager and controlling user permissions. For more information, click here.