Epistemic Tech Reasoning

 As I have already said in a previous post of mine (   Problems with Heroku, Geodjango and Couchbase? Me too!  ), recently i have started using  couchbase  a lot. It offers a variety of cool features that you can read about on their site and make their product attractive. What is more, there are far more interesting stuff for a developer to start using a technology than just a flexible data model. If you like this article, read more at my  updated blog Personally, what i love in couchbase is the super cool  python client , which makes all the everything so simple. There is also tones of documentation and examples, but my experience with the company is deeper than just that. Every time i send them an email they respond immediately, offering great support (even though for the open source community). Enough is enough. Let's talk a bit about coding here. I wanted something much more sophisticated this time. I luckily run into a nice  presentation on elastic search with c

Today it was a long day. I started by wanting to create a simple service that is going to run on  heroku , store some tweets according to some specific keywords that a user is going to type and then provide some trends regarding those. Piece of cake actually, until Heroku started the annoying stuff. My selection for storing the tweets was  Couchbase . It is a really advanced NoSQL database, allowing scaling and many many other interesting facts that anyone playing with big data would love. The problem is, that Heroku does not allow couchbase client libraries to compile on its stack. For that reason i started creating my own buildpack here,  https://github.com/mpetyx/heroku-buildpack-couchbase-geo-django . As you can see, it contains also the popular GeoDjango library. It needs no recommendations, as most of the django developers playing with geospatial data use it. It is a pity that Heroku does not offer a default choice to actually include that library in your app's v