FLUME NG uses channel-based transactions to guarantee reliable message delivery. When a message moves from one agent to another, two transactions are started, one on the agent that delivers the EVENT and the other on the agent that receives the event. In ORDER for the sending agent to commit it’s transaction, it must receive SUCCESS indication from the receiving agent.

The receiving agent only returns a success indication if it’s own transaction commits properly first. This ensures guaranteed delivery semantics between the hops that the flow makes. Figure below shows a sequence diagram that ILLUSTRATES the relative scope and duration of the transactions operating within the two interacting agents.

Flume NG uses channel-based transactions to guarantee reliable message delivery. When a message moves from one agent to another, two transactions are started, one on the agent that delivers the event and the other on the agent that receives the event. In order for the sending agent to commit it’s transaction, it must receive success indication from the receiving agent.

The receiving agent only returns a success indication if it’s own transaction commits properly first. This ensures guaranteed delivery semantics between the hops that the flow makes. Figure below shows a sequence diagram that illustrates the relative scope and duration of the transactions operating within the two interacting agents.