This is part one of a mini-series about working with IBM MQ as a Zato and Python user. This installment will cover installation and configuration whereas the next one will delve into programming tasks.
Zato publish/subscribe message queues and topics
offer several ways to gain insight into the inner workings of all the components taking part in message delivery and this
article presents an overview of the mechanisms available.
are a great choice for high-performance
API integrations. WebSockets have minimal overhead, which, coupled with their ability to
services in a synchronous manner, means that large numbers of clients can easily connect to Zato API servers.
Since version 3.0, it is possible to directly connect Zato clusters and exchange messages as though remote services where running in a local instance. This makes it an ideal choice for environments split into multiple parts.
As an enterprise integration platform and backend, API-oriented, application server, Zato 3.0 ships with Single Sign-On and User Management APIs whose many exciting features are detailed in this blog post.
With the addition of WebSocket channels in Zato 3.0, a question arises of how to combine both HTTP and WebSocket channels in Zato environments. This article shows how a Docker container running in AWS can be configured to expose a single port to handle both kind of requests, including health-status checks from Amazon’s ALB (Application Load Balancer).