Skip to main content

Beanstalkd client/worker sample code

The following code is not tested and there is no defensive coding at all. Those are activities for the reader for now. In the next few days I'll implement the same code in perl and C.  The advantage of this strategy is that some A/B testing and monitoring will let you know which modules need to be rewritten for performance etc... The other side effect is that you can be language agnostic. (I might just try Lua too)

One of the other great side effects of this design is that since there are multiple small applications that are distributed they are easier to debug and extend. (think of all of the advantages of microkernels.)

The Client:
# load the required libraries
import beanstalkc

# make a connection to the beanstalk broker
beanstalk = beanstalkc.Connection(host='localhost', port=14711)

# select the tube that is going to forward the message to your "worker"
# you can have multiple workers listening on the same tube or different tubes
# or a combination.

# this is my message's transaction id, it is also the key used to locate the
# data in the cache and it is the name of the response tube.
msg_id = str(uuid.uuid1())

# HERE store the full transaction in the redis DB and use the msg_id as the key

# start watching the response tube

# send the message to the worker

# wait for a response (timeout is in seconds)
job = beanstalk.reserve(timeout=15)
print job.body

# stop watching the response tube


The Worker:
# load the required libraries
import beanstalkc

# make a connection to the beanstalk broker
beanstalk = beanstalkc.Connection(host='localhost', port=14711)

# setup a watch for incoming messages over the well known tube'msg_for_worker')

while True:
# wait for a request (timeout is in seconds)
job = beanstalk.reserve(timeout=15)
if job:
msg_id = job.body

# HERE we retrieve the message/transaction body from the redis DB. and do our work.

# open a tube to the client response tube

# send the response message to the client


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…