As we are preparing to release
3.2 soon, all the programming examples are being rewritten to showcase what the platform is capable of.
That includes REST examples too and this article presents a few samples taken from the
In this article, we are going to use
in its capacity as a multi-protocol Python API gateway - we will integrate a few popular technologies, accepting requests sent
over protocols commonly used in frontend systems, enriching and passing them to backend systems and returning
responses to the API clients using their preferred data formats.
The fan-out / fan-in pattern
is a staple of more advanced API integrations - let’s check out in practice how,
with Zato, it can simplify asynchronous communication across applications
that do not always exhibit the same kind of availability or performance characteristics.
With the rise of Single-Page Applications (SPA) in web frontends, it is often the case that backend REST APIs
based on Zato need to be configured for CORS. This article will explore what CORS is
and how to make Zato participate in scenarios using it.
In many domains, transfer of static and batch files is an important part of systems integrations and a large number
of applications produce and expect data in the form of files rather than network-based APIs.
In this article, we shall see how
Zato makes multi-protocol integrations of this kind possible in a way that is secure,
scalable and easy to extend in Python.
An integral part of
Zato, its scalable, service-oriented scheduler makes it is possible to execute
high-level API integration processes as background tasks. The scheduler runs periodic jobs which in turn
trigger services and services are what is used to integrate systems.
Enabling rate-limiting in Zato means that access to Zato-based APIs can be throttled
per endpoint, user or service - including options to make limits apply to specific IP addresses only - and if
limits are exceeded within a selected period of time, the invocation will fail. Let’s check how to use it all.