Zato Blog

Open Source ESB, APIs, AI
and Cloud Integrations in Python

Topic: rest

post 1 image
While Zato can support AMQP, WebSphere MQ, ZeroMQ or FTP as well, the majority of environments will use the ubiquituous HTTP protocol only and this post describes the traffic patterns within a typical HTTP-only cluster consisting of a load-balancer, web admin, Redis, SQL ODB and two servers, right after it’s been installed without any user-specific customizations.

Topics:REST

post 2 image
A Zato ESB and application server feature that has just been added on GitHub is an HTTP access log. This is an additional log to what has been already available in regular server logs and keeps nothing but information regarding HTTP requests in a format used by Apache httpd. This makes it possible to use existing tools in order to parse and extract interesting information out of the logs.

Topics:REST

post 3 image
Overview It has been possible to create reusable REST services in Zato right from the release 1.0 however a feature that recently landed in GitHub and that will be released in Zato 2.0 makes it easier to use of RESTful URLs, also known as clean URLs. This blog post presents HTTP channels and an upcoming one will deal with HTTP outgoing connections. The goal The diagram below depicts what we’d like to achieve - 3 independent applications invoking the same service yet each using separate URLs.

Topics:REST

post 4 image
A feature that has been recently added to Zato in git and will be released in version 2.0 is an HTTP request profiler.

Topics:REST

post 5 image
This how-to shows what is needed to invoke JSON-based web services using Zato, which is a Python-based ESB for SOA, cloud integrations and backend services.

Topics:REST

post 6 image
Imagine, or recall, a scenario. You integrate three applications, two client HTTP ones and the third is a backend one (no matter the technology) […]

Topics:REST