Thinking about how your master dataset is stored and managed is arguably the most important part of architecting a data-driven system. Your master dataset is your source of truth. An issue here, be it hardware failure, human error, or something else, could easily result in irreparable damage to some or all of your data.
Some photos from my day visiting the Royal Greenwich Observatory and the Cutty Sark.
Update: I’m now using BitBucket Pipelines instead.
I’ve recently starting making my own Granola.
I mentioned a few weeks ago that whilst moving my blog to S3 I hit a hard limit of 50 redirects, meaning I would break some URLs if I made the move.
I’m in the process of moving this site to Amazon S3, rather than hosting it myself on a VPS.
Some notes after attending this years Container Camp in London.
I’ve been looking at using Finagle as a web endpoint for a side project app.
An excellent essay by Bob Nystrom on the concepts of asyncronous programming, and how various programming languages apply these concepts.
Say you have an application that collects data from a number of sources and stores it somewhere.