Tecnologías en Tenea


AMQP

Transport
Peer-to-Peer
Topology


The API implementations see more detail, under the covers of AMQP.

In addition to MOM messaging, they have to deal with the details of maintaining and securing a network connection between the client and the broker.
This is how the lower level transport stack looks to a systems engineer.

AMQP
1

Tecnologías en Tenea


AMQP
Broker-to-Broker
Global
Forwarding


Global addressing will relay messages
from local queues on a client-local
broker to queues resident on the
destination organisations broker.

This is very similar to SMTP.
Also, as with SMTP relaying is strongly discouraged as it may compromiser.

AMQP
2

Tecnologías en Tenea


AMQP
End-to-End
MOM Topology
(WORK+)


This is the message transmission path
as the sending and receiving applications
perceive it.

It is important to note that the Message
transmission path is a game of
two halves; the deposit in a queue
half, and the collect from the queue
half.

This decoupling of sender and recipient
is the prime purpose of message
oriented middleware.

AMQP
3

Tecnologías en Tenea


AMQP

Model Entity
Relationship
Diagram


This diagram shows the perceived
entities which the client an discover in
a compliant broker, and the relationships between them.

A compliant broker may be implemented differently, but MUST exhibit these same perceivable entities.

AMQP
4

Tecnologías en Tenea


AMQP

Queue Entry
Detail
(WORK NEEDED)


AMQP
5

Tecnologías en Tenea


AMQP

Delivery into
Message
Queues

Delivery into queues is the first half of
the end-to-end MOM delivery process.

AMQP
6

Tecnologías en Tenea


AMQP

Consumption
from Message
Queues

I'm using the name “Stable Queues”
(a la Stable Storage) to encompass
the idea of a safety-deposit-box style
drop-point.

Collecting Messages from Queues in a
configurable way is the second half of
the MOM end-to-end process.

AMQP
7

Tecnologías en Tenea


AMQP

Message
Consumer /
Queue Receiver

Here, the JMS Selector concept is
modelled using AMQP Selector + Consumer to pick Messages from the
Queue.

AMQP
8

Tecnologías en Tenea


AMQP

PubSub can be
implemented
in 2 ways

1. MessageConsumer
2. TopicSubscriber

Here, the JMS Selector concept is
modelled using a Queue to represent
the Topic and AMQP Bindings to route
Messages from the Topic using Topic
Bindings to copy the Messages into
Private Queues, one Private Queue for
each subscriber to the Topic.

AMQP
9

Tecnologías en Tenea


AMQP
Message
Consumer /
Durable Topic
Subscriber

 

Here, the JMS Selector concept is
modelled using a Queue to represent
the Topic and AMQP Bindings to route
Messages from the Topic using Topic
Bindings to copy the Messages into
Private Queues, one Private Queue for
each subscriber to the Topic.

AMQP
10

Tecnologías en Tenea


AMQP

Global Addressing
Internet
Subscription

The aim of Global Subscription Relay
is to enable de-queuing of information
from a well known Address Queue
within another organisation, whilst
adhering to good Internet Security
practices.

The direction of connection initiation
should always be from higher trust
zones to lower trust zones.
Because of the active nature of this
activity, concerns to robustness and
prevention of resource abuse are
paramount...

AMQP
11

Tecnologías en Tenea


AMQP

Global Addressing –
Internet
Subscription


AMQP
12