<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Sre on Hashbang.ca</title>
		<link>https://hashbang.ca/tag/sre</link>
		<description>Recent content in Sre on Hashbang.ca</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 07 Apr 2016 03:01:00 -0700</lastBuildDate>
		
			<atom:link href="https://hashbang.ca/tag/sre/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Book review: Site Reliability Engineering</title>
				<link>https://hashbang.ca/post/book-review-site-reliability-engineering</link>
				<pubDate>Thu, 07 Apr 2016 03:01:00 -0700</pubDate>
				<guid>https://hashbang.ca/post/book-review-site-reliability-engineering/</guid>
				<description>&lt;p&gt;Google has been working for about 2 years on a book about Site Reliability Engineering, the discipline and organization that keeps Google&amp;rsquo;s large-scale systems running smoothly. &amp;ldquo;Site Reliability Engineering&amp;rdquo; was finally published last week. It spans some 500 pages, and offers a rare inside glimpse into how Google actually works. The authors are remarkably open, naming technologies and projects, and explaining how systems work. There may not be source code, but there&amp;rsquo;s lots here that can be implemented outside Google. That makes it a great read for startups expecting to scale and small-to-medium tech companies that want to up their reliability game.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
