A newly added Zato feature lets one update HTTP timeouts on fly, without any redeployments.
It's been always possible to provide a timeout a given HTTP connection should be capped to. However, changing the value required either redeploying a service or storing it in an external store, such as Redis, that was queried each time a request was made. While being very lightweight, these operations still were something to remember about.
The feature will be released in Zato 2.0 but it's already available in git master.