Q:

Build durable architecture with Websphere MQ clients

How can you create a durable architecture environment using MQ Client and server if the clients don't allow you to persist messages nor do they allow for assured delivery? 
Just trying to figure out how you can build a salable / durable architecture if the clients don't appear to contain any of the necessary components required to persist data.  
Thanks,
S

A:

Middleware messaging was born of the need to persist data locally to mitigate the effects of failures of the remote node or of the network.   The idea at the time was that the queue manager was installed locally on the box where the application lives and was treated as part of the transport stack.   For instance you might install TCP and WMQ as a transport and some apps would use TCP while others used WMQ. 
In the intervening 20 years, the original problems that led to the creation of MQSeries (Now WebSphere MQ) have largely been solved.   The networks have improved by several nines of availability and high availability hardware and software clustering have provided options to keep the different components available 24x7. 
So the practices in widespread use today to address your question follow two basic approaches.   Either make the components highly available so that the client can always find a messaging server, or put a QMgr where the application lives in order to provide local queueing.