Varnish Software: Zipnish for microservices

8:00 am Varnish Software marketing meeting, Oslo, Norway.

Branding guru: Okay, so we need a name for the new Varnish Software open source tool for microservices performance tracking.


Team members: Hmm, how about MicroTracker? Or maybe MicroPerform?

Branding guru: Okay, so hear me out, I was thinking — Zipnish.

** silence **

Team members: Yeah, no, we like it, we see what you did there.

Well Zipnish it is, whether you get the naming convention or not (keep reading and all will become clear) — this is indeed a new open source tool that tracks performance and helps resolve latency issues in microservices architectures .

Available on Github, Zipnish claims to give developers insights on the status of each microservice component regardless of development and deployment architecture.

“Companies use Varnish Cache for speeding up a lot different things, not just websites”, explains Per Buer, founder and CTO of Varnish Software.

“Microservices is one of those popular use cases. Several Varnish Cache users have been asking us for an easy way to track the performance of individual microservices regardless of architecture. We had the ingredients to easily build this and decided to open source it to allow our community to reap the benefits of this new project.”

Gaining insights into how quickly services are running or if they are adding latency is a difficult task in distributed architectures such as microservices.

First Zipkin, now Zipnish

Twitter developed the open source software Zipkin in 2012 to address this issue, however it only supports Java architectures.

So then, Varnish now launches Zipnish in response to demand for an architecture-agnostic open source tool.

For example, a customer had been using Varnish Cache for stateless microservices, central caching and cache invalidation in its microservices environment but needed a tracing tool that would also work with .net.