Replicating with Datomic
February 11, 2017
I will focus in this post on a practical application of replikativ. I will talk more about the theoretical underpinnings and motivations in the next post. So in this concrete example we want to store tweets. The whole code is available here. We do not know yet what we want to do with them exactly, but we want to have a straightforward way to access them later. This is what replikativ was built for: An open data management layer as a baseline for distributed applications. Actually local applications are a subset of distributed applications, so this means all computer programs. This generality is not meaningful here though.
Unified storage IO
November 12, 2016
Why not just use store X?
Durability should be simple and flexible. When I started to design replikativ I investigated many different IO options, including many key-value or document stores like CouchDB, Riak, MongoDB, IndexedDB etc.
Erlang inspired error handling with superv.async.
March 10, 2016
Clojure error handling
Proper error handling is hard. I have struggled with it often without recognizing it. You might think that you can add
try-catchmechanisms to sections you find prone to error, typically sections doing IO with remote systems and services.
Welcome to my blog.
March 10, 2016
On this blog I will track different issues I am facing in the pursuit of distributed systems, including direct implementation aspects and issues with replikativ. Additionally I will write about different machine learning topics I am involved in. I hope you find it useful, feedback is appreciated!