As a note, if you find errors with the math below, please let me know.
This cost comparison only compares cost per I/O operation. It does not discuss storage or transit costs.
| console.reset = function () { | |
| return process.stdout.write('\033c'); | |
| } |
idempotent operations to store service metrics: we weren't able to come up with a good solution to this.
our rule of thumb for network failures was that packets will get lost, so you can have two behaviors for server operations:
at LEAST once: if a response gets lost, retry. you may end up doing the same operation twice.
at MOST once: if a response gets lost, give up. the operation might have been lost before the server saw it.
if your operations are idempotent, you can use "at least once" mode for everything. we did that for almost every server i can think of. it was an explicit design goal of flock (the social graph database) and finagle (the server-building toolkit).
| background: -webkit-gradient(linear,left top,left bottom,from(#ff0052),to(#8e2b88)); | |
| -webkit-background-clip: text; | |
| -webkit-text-fill-color: transparent; |
| $.preloadImages = function() { | |
| for(var i = 0; i<arguments.length; i++) { | |
| $("<img />").attr("src", arguments[i]); | |
| } | |
| } | |
| $(document).ready(function() { | |
| $.preloadImages("hoverimage1.jpg","hoverimage2.jpg"); | |
| }); |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
| git submodule foreach '[ "$path" == "submodule-to-exclude" ] || git pull origin master' |
Normally git diff would color additions green and deletions red. This is cool, but it would be even cooler if it adds syntax highlighting to those lines. This is a git pager that does so.
It parses the diff output and picks up the SHAs of files with additions and deletions. It uses [CodeRay][coderay] to highlight each file and then it extracts the lines that are shown in the diff. It then uses [term/ansicolor][color] to make a gradient from the CodeRay color and the diff color (red for deletion, green for addition) and uses it to replace the original.
I tried using rugged instead of shelling out to git show – it was faster overall, but it did incur a noticeable start up time.
Check out the image below for a demo.
I'm still very new to Kafka, eventsourcing, stream processing, etc. I'm in the middle of building my first production system with this stuff and am writing this at the request of a few folks on Twitter. So if you do have experience, please do me and anyone else reading this a favor by pointing out things I get wrong :)
