In part, the use of AMQP is incidental. The team behind skupper had
been working on AMQP based systems previously but realised that the
router that now underpins skupper had much wider relevance.
A useful feature of AMQP is the symmetric nature. Whereas HTTP has
strict roles for client and server, AMQP does not. This is what at
present allows skupper to offer bidirectional service invocation where
firewall rules or NAT allows TCP connection establishment in only one
direction. This can certainly be achieved with other protocols
however.
My view, which is not necessarily shared by others, is that AMQP is
merely an implementation detail at present, and is an artefact of the
evolutionary origins of the project.