3.1 - 2019-06-18


Want to quickly install Zato? Check out this Dockerfile which will set up a fully working cluster with 2 servers, load-balancer and web-admin in 10 minutes.

  • Enhanced support for Docker, including Quickstart, Swarm and Kubernetes
  • Added support for Python 3.6+ in addition to Python 2.7
  • Added MongoDB connections
  • Added LDAP connections, including Active Directory
  • Added Microsoft SQL Server connections
  • Added Apache Kafka connections
  • Added SFTP connections
  • Added instant messaging connections: Slack and Telegram
  • Added outgoing WebSocket connections to already existing channels
  • Added JSON-RPC channels
  • Added rate limiting - exact and approximate
  • Added IP whitelisting
  • Added a JavaScript client for Zato services and message topics
  • Extensions to Single-Sign On: two-factor authentication and multi-credentials accounts
  • Added means to list SSO user sessions
  • Added Accept headers configuration to REST channels
  • Multiple REST channels may now reuse URL paths as long as their HTTP methods differ
  • Added JSON Schema validation
  • Added ability to connect Zato clusters using WebSockets, including subscriptions to events in other clusters
  • Added means to broadcast messages to all WebSocket clients in addition to invocations of individual ones
  • Added TOTP two-factor authentication to web-admin
  • Added TLS to AMQP connections
  • Servers start and stop up to several times faster than previously
  • When creating new servers, usage of TLS CA is no longer required
  • Deploying base services will automatically redeploy any services subclassing them
  • General performance boosts, particularly in the area of REST connections
  • Dropped support for RHEL/CentOS 6 (v.7 is still fully supported)

3.0 - 2018-06-30

2.0 - 2015-01-28

1.1 - 2013-06-02

  • Unified installer for Ubuntu, Mint, Fedora and OS X
  • Added the zato check-config command
  • Fixed a bug which lead to double execution of user-defined scheduler jobs
  • Made quickstart clusters more robust when confronted with improperly configured servers, sanity checks are now performed before servers are started
  • Changed the default value of main.deployment_lock_expires so it works on 32-bit systems without a need for reconfiguring servers after they’re created
  • Made scripts generated by zato quickstart relocatable
  • Newly created servers start CPU_COUNT gunicorn workers by default now, not CPU_COUNT * 2 as previously
  • HAProxy load-balancer can now bind to all interfaces. Patch provided by Myroslav Opyr (quintagroup.com).

1.0 - 2013-05-18

  • Initial release