Since I've been working on Zarkov, I've been writing a few map/reduce jobs. One of the things I noticed about map/reduce, at least as I've implemented it in Zarkov, is that it's pretty inefficient if you want t o generate several aggregate views of the same data (like say an event stream). In order to meet Zarkov's performance requirements without making my operations team too angry, I decided to "extend" map/reduce, as it's implemented in Zarkov. I'm not terribly creative, so I called this command xmapreduce
. Here' I'll briefly describe map/reduce, show the problem with it, and explain the solution implemented in Zarkov.... read more
Over the past few weeks I've been working on a service in Python that I'm calling, in the tradition of naming projects after characters in Flash Gordon, Zarkov. So what exactly is Zarkov? Well, Zarkov is many things (and may grow to more):
Over the past few weeks I've been working on a service in Python that I'm calling, in the tradition of naming projects after characters in Flash Gordon, Zarkov. So what exactly is Zarkov? Well, Zarkov is many things (and may grow to more):
Over the past few weeks I've been working on a service in Python that I'm calling, in the tradition of naming projects after characters in Flash Gordon, Zarkov. So what exactly is Zarkov? Well, Zarkov is many things (and may grow to more):
Over the past few weeks I've been working on a service in Python that I'm calling, in the tradition of naming projects after characters in Flash Gordon, Zarkov. So what exactly is Zarkov? Well, Zarkov is many things (and may grow to more):
In the next few posts, I'll be going over each of the components of Zarkov and how they work together. Today, I'll focus on Zarkov as an event logger. ... read more