Zato 3.0.0 documentation

Get support →

3.0 - 2018-06-30

Note

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.

• A built-in multi-protocol message broker with publish/subscribe topics and guaranteed delivery queues
• Single Sign-On and user management API
• SAP connections
• IDE plugins for PyCharm and Visual Studio Code
• New caching layer
• Memcached connections
• Security mechanisms to help in achieving compliance with PII regulations (e.g. GDPR, HIPAA or PDPA)
• Automatic API documentation generation - Sphinx, OpenAPI/Swagger and WSDL
• WebSocket channels and outgoing connections
• SMS messaging with Twilio
• HashiCorp Vault security definitions
• JSON Web Token security definitions (JWT)
• Extended hot-deployment to work with static files, including JSON, XML, CSV or any other format
• General performance improvements let Zato servers run up to several times faster - applies to HTTP, AMQP, ZeroMQ and IBM MQ connections
• Reduced RAM consumption through ability to disable selected internal components
• AMQP, ZeroMQ and IBM MQ connections can now be synchronous
• New crypto mechanisms: encryption and decryption, hashing as well as generation of passwords and secrets
• Added passwords to servers
• New server startup hooks and callables
• Scheduler now runs as its own component managed from command-line interface
• Added optional gzip encoding to REST and SOAP channels
• New CLI commands:
  • zato hash get-rounds to compute PBKDF2 rounds for secrets hashing
  • zato sso create-user, create-super-user, delete-user, change-user-password, reset-user-password, lock-user and unlock-user for SSO users management
• Added an internal startup cache that makes servers boot up to several times faster
• Servers now cache internal services on first boot - improves startup time up to several times
• Removed technical accounts - already superseded by API keys in 2.0
• Removed the HTTP-only audit log
• Dropped support for SQLite under RHEL 6 (RHEL 7 and other systems continue to support it)

2.0 - 2015-01-28

• Dockerfile to set up a full-featured cluster with 2 servers, load-balancer and web-admin in 10 minutes
• REST services, channels, outgoing connections and a helper JSON adapter
• Redis-based REST publish/subscribe
• :HTTP GUI Audit Log for requests and responses
• Patterns: fan-out/fan-in, parallel execution and invoke/retry
• Cloud Amazon S3
• Cloud OpenStack Swift connections and notifications
• SQL notifications
• Cassandra connections and pre-compiled CQL query templates
• Solr
• ElasticSearch
• Odoo/OpenERP connections
• SSL/TLS for channels and outgoing connections
• Role-based access control (RBAC) for HTTP channels
• OAuth
• XPath-based security
• API keys-based security
• NTLM security
• Amazon AWS security
• Support for SQLite
• Support for MySQL
• SMTP
• IMAP
• JSON Pointers
• XPath and XML Namespaces
• JSON serialization in HTTP outconns
• SOAP invocations with suds and WSDL prefetching
• Outgoing HTTP timeouts
• New Relic integration
• Sentry integration
• Redis HA with sentinels
• Statistics in Redis pruned periodically
• Message mappers
• Distributed locks
• Date/time utils
• Dictionary and list message navigation
• New Simple IO (SIO) types: CSV, Dict, Float, List, ListOfDicts, Opaque
• Added RPM packages for RHEL/CentOS 7
• Bash completion in CLI
• Ability to specify user locale in servers (i.e. en_GB.UTF-8)
• Startup scripts to start Zato environments when an OS starts
• Framework for API testing (https://github.com/zatosource/zato-apitest)
• Ability to output HTML in services using Django templates
• Logging configuration migrated to YAML
• Ability to hot-deploy code directly from a repository checkout (i.e. from GitHub)
• Configuration patterns to fine tune which services can be deployed and invoked
• Means for invoking services on selected servers only
• New hook (accept) for filtering out requests that a service cannot process
• Improved logging- Apache-like HTTP access log for servers, compatible with popular log parsing tools, logging config uses YAML, subsystems have their own log files, web-admin’s logs show IP of the user connecting to it
• Ability for users to store configutation in their own INI-style files
• zato –version is clearer what exact git commit was used to build it
• Quickstart scripts remove stale PID files automatically
• Started using async Postgres driver to improve performance
• Made zato start command work much faster
• Alembic migrations to ease with upgrades across releases
• Ability to run servers in Python shell
• Made service listings in web admin much faster
• Ability to dump threads and greenlets on a user signal
• User-defined Lua functions for Redis
• New tests run prior to starting of components make sure the latter are correctly configured
• Command to run ipython with Zato-related packages on PYTHONPATH
• Startup services invoked when a server is starting
• OpenID in web admin
• Constants in zato.common.broker_message became wrappers around integers - use .value attribute to reference them. For instance, SERVICE.PUBLISH.value instead of SERVICE.PUBLISH.
• Added a hot_deploy.delete_after_pick_up flag, setting of which to False will prevent Zato from deleting hot-deployed Python code effectively making servers work in a live-reload mode
• Made HTTP Basic Auth passwords optional
• Made it possible to specify an HTTP method to ping outgoing HTTP/SOAP connections with
• Added the ability to specify the size of each outgoing HTTP/SOAP connection’s pool size (this is a per-worker setting)
• Made Service.log_input/output log the user_msg as a prefix of the dictionary of data to write out, not as part of its keys

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

Last update:

Apr 01, 2019