<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: bourbonproof</title><link>https://news.ycombinator.com/user?id=bourbonproof</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 11 Jun 2026 02:51:55 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=bourbonproof" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by bourbonproof in "PgDog is funded and coming to a database near you"]]></title><description><![CDATA[
<p>the reason mongo is a joy to use in scaled env is because no additional setup/software needed and all drivers natively support secondary/primary writes/reads and topological changes. so it's end to end, and adding is as a new proxy in frontend of postgres leads to all clients being incompatible or the code itself has no control anymore about when to use a secondary and what allowed stall is acceptable for a particular query. Any solutions to this by pgdog?</p>
]]></description><pubDate>Wed, 10 Jun 2026 14:41:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=48477025</link><dc:creator>bourbonproof</dc:creator><comments>https://news.ycombinator.com/item?id=48477025</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48477025</guid></item><item><title><![CDATA[Show HN: Papernews – self-hosted daily newspaper PDF for your reMarkable]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/marcj/papernews">https://github.com/marcj/papernews</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48406065">https://news.ycombinator.com/item?id=48406065</a></p>
<p>Points: 12</p>
<p># Comments: 4</p>
]]></description><pubDate>Thu, 04 Jun 2026 23:28:26 +0000</pubDate><link>https://github.com/marcj/papernews</link><dc:creator>bourbonproof</dc:creator><comments>https://news.ycombinator.com/item?id=48406065</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48406065</guid></item><item><title><![CDATA[New comment by bourbonproof in "Flightcontrol: A PaaS that deploys to your AWS account"]]></title><description><![CDATA[
<p>Honestly, Docker Swarm is so great. We use it with 6 very beefy machines (each 1tb memory/96cpu cores) for years already. It's so stable and well done, no restarts, crashes, or weird behaviors. We use it in a Hetzner VLAN and performance is excellent. We are very satistfied with it, and I would use it for even bigger scenarios. I even thought about building something like coolify/flightcontrol on top of it, so I can really easy have  proper deployments of my stuff</p>
]]></description><pubDate>Tue, 07 Oct 2025 00:16:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=45497862</link><dc:creator>bourbonproof</dc:creator><comments>https://news.ycombinator.com/item?id=45497862</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45497862</guid></item><item><title><![CDATA[New comment by bourbonproof in "PlanetScale for Postgres is now GA"]]></title><description><![CDATA[
<p>Do I understand this right: if these 3 nodes shutdown for some reason, all data is lost and you have to actually restore from backup instead of just starting the machine again. And even if you have to restart one node (due to updates, or crashes) you also have to restore from backup?
If so, why not pick a hosting provider that doesn't wipe the disk when machine shuts down?</p>
]]></description><pubDate>Mon, 22 Sep 2025 22:49:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=45340587</link><dc:creator>bourbonproof</dc:creator><comments>https://news.ycombinator.com/item?id=45340587</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45340587</guid></item></channel></rss>