I’ve set out to solve: How to synchronize “low volume” parts of a database to a frontend in realtime exclusively for reads. In this scenario, “low volume” means few entries with a low update frequency. Let’s say we’re talking about less than a thousand entries affected by fewer than ten updates every minute across all entries.
Read more...
Poor software quality stems from inexperience, time constraints, and software decay, but these can be countered by prioritizing quality. Not prioritizing quality leads to inefficiencies like slow delivery and higher costs. Investing in maintainability ensures long-term success. Read more... During code reviews I’ve seen the following repetition pattern a lot. I am going to use Clojure to illustrate, but it also happens in other programming languages:
Read more...I’ve released a small Clojure InfluxDB client library since my last post on the same subject, and as I mentioned I wanted to explore ways to leverage the /write endpoint.
I’m working on a project where a time series database makes sense and the choice fell on InfluxDB. I found mnuessler/influxdb-clojure an aged Clojure wrapping an older version of the Java InfluxDB client. Being all excited about diving into this new area I thought it would be best to leverage the existing efforts put into making InfluxDB accessible in Clojure. It took me a while to realize that I wasn’t comfortable with all the layers put between me and InfluxDB server.
Read more...