startup callable objects are a means through which arbitrary Python functions or classes can be invoked when
a server is booting up in order to influence its configuration or setup, even before any service is invoked.
This technique offers customization possibilities in addition to the standard configuration options set
before a server starts - read on to learn details.
One of the exciting additions of the upcoming Zato 3.2
release is the ability to
invoke services through OpenAPI endpoints without a need for creation
of REST channels explicitly - read more for details.
Acting as containers for enterprise APIs,
services are able to invoke each other to form higher-level processes and message flows. What if a service
needs to invoke a hot-deployable Python function or method, though? Read on to learn details of how to accomplish it.
A recurring need in larger integration projects is generation of API documentation for users belonging to different,
yet related, target groups. Read on to learn how to generate Zato-based API specifications for more than one group
from a single source of information.
This article presents a workflow for auto-generation of API specifications for your
services - if you need to share your APIs with partners, external or internal, this is how it can be done.
If you need to configure
connections and you want to ensure the highest performance possible, this is the post which goes through the process step-by-step. Read on for details.
This article introduces features built into
that let one take advantage of
topics and message queues in communication between Zato services, API clients and backend systems.