Building scalable, high-performance API and AI integrated environments requires a consistent vision
and tenets to establish it on. From this article, you can learn how to design your own API and AI architectures
based on what our vision is and how it is executed.
This Zato how-to is about ensuring that only API clients with valid SSL/TLS certificates,
including expected certificate fingerprints or other metadata, can invoke selected REST endpoints.
In this way, we are making access to the endpoints secure and, at the same time, we can
guard against a class of faults related to the Certificate Authority infrastructure.
Even if most of new APIs today are built around REST, there are still already existing,
production applications and systems that expose their APIs using SOAP and WSDL only -
in today’s article we are integrating with a SOAP service in order to expose
it as a REST interface to external applications.
The seemingly simple zato --version command packs in several interesting details that are helpful in understanding
what Zato version one currently uses - let’s find out what they all mean.
Zato WebSocket channels let you accept long-running API connections and, as such, they have a few settings
to fine tune their usage of timeouts. Let’s discover what they are and how to use them.
One of the additions in the upcoming Zato 3.2 release of is an extension to its publish/subscribe mechanism that lets services publish messages directly to other services. Let’s check how to use it and how it compares to other means of invoking one’s API services.
How does it work? In your Zato service, you can publish a message to any other services as below. Simply point self.pubsub.publish to the target service by the latter’s name and it will receive your message.
In this article, we will cover the details of how Zato
SQL connection pools can be configured to take advantage of features and options
specific to a particular driver or to the SQLAlchemy library.
Today, we are looking at how environment variables can be used to let the configuration of your
Zato-based API services be reusable across environments - this will help you centralise all
of your configuration artefacts without a need for changes when code is promoted across environments of different levels.
Using Zato, it is easy to make IBM MQ queues available to Python applications -
this article will lead you step-by-step through the process of setting up the Python integration platform to listen for
MQ messages and to send them to MQ queue managers.
This article is an excerpt from the broader set of changes to our documentation in preparation for
Zato. Read it to learn more about Zato and the usage of Python
in API integrations.