components

This section aims to provide an understanding of the fundamental components of which casual consists.

Each component has a manager that has the responsibility of the component

The following diagram illustrates all managers and their relationships.

manages

domain-manager

Responsibilities:

  • Start all other managers

  • Hold domain configuration datastructure

  • Start all user servers and executables

  • event relay/dispatch

  • Provide pending message service for other managers

  • Notify subscribers when processes terminate/dies

service-manager

Responsibilities:

  • Service lookup repository

  • Any running process that has services will advertise these to service-manager

transaction-manager

Responsibilities:

  • Start all configured resource proxies

  • Coordinate (distributed) transactions

  • Act as a resource to other domains

gateway-manager

Responsibilities:

  • Listen to configured addresses and ports

  • Start configured outbound connections

  • Start inbound connections, when other domains connect with their outbound

gateway-outbound

  • Forward messages to the other end (strict defined protocol)

  • Act as a resource to transaction-manager (if invocations are in transaction)

queue-manager

Responsibilities:

  • Start all configured queue-groups

  • Queue lookup

queue-group

  • Provide configured queues

  • Guaranteed transactional persistent messages (if configured)

  • Act as a resource to transaction manager