GridServer Architecture

DataSynapse GridServer has four different components in its architecture:

•

Grid Clients — The components that submit service requests to the Grid. Also called Drivers.

•

Engines — The processes that host and run services on the Grid nodes.

•

Brokers — The component that provides request queuing, scheduling and load-balancing. Brokers are also responsible for managing Engines.

•

Directors — The component that assigns Grid Clients and Engines to Brokers based on policy. They manage and load balance Engines across available Brokers.

Engines and Grid Clients log in to the Director and are authenticated; the Director then routes the Engines and Grid Clients to available Brokers.

Grid Clients submit requests through the Broker. Engines receive work requests from the Broker, and in most cases, exchange data directly with the Grid Clients. This allows the system to be highly scalable. Since the Brokers manage all work requests, load balancing is optimal and resilience is built into the system.

Brokers manage Engines and Drivers, and schedule work with lightweight messages. Drivers and Engines exchange work data directly when using Direct Data Transfer.