Skizze: Behind the Scenes of Alpha 2

Based on the feedback we got for our initial alpha release, we worked on improving Skizze and moving the project forward. To recap, Skizze is a sketch data store to deal with all problems around counting and sketching using probabilistic data-structures. My old time hacking buddy Neil Patel, who is also Xamarin Insights Technical Lead and Architect, blogged about the latest release, and also provided some background on why Skizze exists, and how to get started. This second alpha focuses mainly on improving development and operating experience. It is an early alpha so don't expect much, but hopefully now it

Skizze progress and REPL

 Big Data, Data Science

Over the last 3 weeks, based on feedback we proceeded fledging out the concepts and the code behind Skizze. Neil Patel suggested the following: So I've been thinking about the server API. I think we want to choose one thing and do it as well as possible, instead of having six ways to talk to the server. I think that helps to keep things sane and simple overall. Thinking about usage, I can only really imagine Skizze in an environment like ours, which is high-throughput. I think that is it's 'home' and we should be optimising for that all day

Skizze - A probabilistic data-structures service and storage (Alpha)

 kde, Go, Algorithms, Big Data

At my day job we deal with a lot of incoming data for our product, which requires us to be able to calculate histograms and other statistics on the data-stream as fast as possible. One of the best tools for this is Redis, which will give you 100% accuracy in O(1) (except for its HyperLogLog implementation which is a probabilistic data-structure). All in all Redis does a great job. The problem with Redis for me personally is that, when using it for 100 of millions of counters, I could end up with Gigabytes of memory. I also tend to

Counting flows (Semi-evaluation of CMS, CML and PMC)

 Go, Algorithms, Big Data

Assume we have a stream of events coming in one at a time, and we need to count the frequency of the different types of events in the stream. In other words: We are receiving fruits one at a time in no given order, and at any given time we need to be able to answer how many of a specific fruit did we receive. The most naive implementation is a dictionary in the form of <string, int>, and is most accurate and suitable for streams with limited types of events. Let us assume a unique item consists

Ich bin ein Xamarin(er) ♥

As of the beginning of the April I am a Xamarin (that is what Xamarin employees call themselves). At Xummit I met the rest of the Xamarins and I had an incredible time there (dare I say magical ♥). I met old friends like Rodrigo Moya, Jason Smith, David Siegel, Cody Russell, Neil Patel, Connor Curran, Gord Allot and others, but also made new friends: Zack Gramana: The right amount of crazy and creative. He is helping me with my new pet project. Seth Rosetter: SF chilled out hacker with an ear for techno and extreme positive attitude, a delight to