<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Platforms on Bill Glover</title>
		<link>https://old.bill.dev/tags/platforms/</link>
		<description>Recent content in Platforms on Bill Glover</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
			<managingEditor>hello@bill.dev (Bill)</managingEditor>
		
		
			<webMaster>hello@bill.dev (Bill)</webMaster>
		
		
		
			<lastBuildDate>Sun, 28 Sep 2025 22:27:35 +0100</lastBuildDate>
		
			<atom:link href="https://old.bill.dev/tags/platforms/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The importance of Health Probes</title>
				<link>https://old.bill.dev/2020/04/30/the-importance-of-health-probes/</link>
				<pubDate>Thu, 30 Apr 2020 20:35:35 +0000</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/2020/04/30/the-importance-of-health-probes/</guid>
				<description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Organisations of all sizes are now deploying applications to platforms such as Kubernetes. Many of these applications do not adopt cloud native practices. Often the excuse is application age or product limitation.&lt;/p&gt;&#xA;&lt;p&gt;Many teams invest in platform infrastructure but failed to capitalise on these benefits. So what gives? Are platforms overhyped? Are the complexities of the enterprise too much for modern platforms?&lt;/p&gt;&#xA;&lt;p&gt;Engineers deploy applications to Kubernetes to take advantage of common platform features. Many of these features claim to help maintain service availability including:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
