Over a million developers have joined DZone.
Platinum Partner

Replace HTTP RPC Calls With ZeroMQ

The Integration Zone is brought to you in partnership with 3scale. Take control of your APIs and get a free t-shirt when you complete the 3step Challenge

HTTP is the most common choice for internal RPC service calls, but you may not have known that you can use ZeroMQ for this and probably get better results.  Here are a few reasons why from this great post on augustl.com:

In summary, the benefits ZeroMQ offers over HTTP are:

  • Multiple concurrent RPC calls over the same TCP connection. With HTTP, you're limited to sequential calls (keep-alive). This is a big one.
  • No manual connection management. This isn't impossible to do with HTTP, and is mostly a library problem, but AFAIK few libraries exist that lets you do this right with HTTP.
  • Supports multiple server processes responding to requests. No HTTP load balancer needed.
  • No manual retry handling. Can stop the server, do a RPC, then start the server, then get a response - the message is queued, instead of delivered directly.

    -- augustl.com


The blog goes on to show you how to take advantage of ZeroMQ RPC service calls with a little bit of Clojure code.

The Integration Zone is brought to you in partnership with 3scale. Learn how API providers have changed the way we think about integration in The Platform Vision of API Giants.

Topics:

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}