<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Game-Day Exercises on Brave New Geek</title><link>https://bravenewgeek.com/tag/game-day-exercises/</link><description>Recent content in Game-Day Exercises on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 12 Nov 2014 17:00:25 -0600</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/game-day-exercises/index.xml" rel="self" type="application/rss+xml"/><item><title>Sometimes Kill -9 Isn’t Enough</title><link>https://bravenewgeek.com/sometimes-kill-9-isnt-enough/</link><pubDate>Wed, 12 Nov 2014 17:00:25 -0600</pubDate><guid>https://bravenewgeek.com/sometimes-kill-9-isnt-enough/</guid><description>&lt;p&gt;If there’s one thing to know about distributed systems, it’s that they have to be &lt;a href="http://www.artima.com/intv/distrib.html"&gt;designed with the expectation of failure&lt;/a&gt;. It’s also safe to say that most software these days is, in some form, distributed—whether it’s a database, mobile app, or enterprise SaaS. If you have two different processes talking to each other, you have a distributed system, and it doesn’t matter if those processes are local or intergalactically displaced.&lt;/p&gt;</description></item></channel></rss>