<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: farsa</title><link>https://news.ycombinator.com/user?id=farsa</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 30 May 2026 21:10:21 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=farsa" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by farsa in "Building durable workflows on Postgres"]]></title><description><![CDATA[
<p>Making the workflow engine of DBOS depend on the paid component (Conductor) for scaling and recovery makes it a no-go. River also has "traps" like not supporting DLQ, which is a paid feature.</p>
]]></description><pubDate>Thu, 28 May 2026 23:34:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=48317032</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=48317032</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48317032</guid></item><item><title><![CDATA[New comment by farsa in "Does Postgres Scale?"]]></title><description><![CDATA[
<p>DBOS looks simple (good), but from the docs below, executor elasticity appears to be locked behind license purchase. So it truly is like docker compose, good and bad parts?<p><a href="https://docs.dbos.dev/production/workflow-recovery#recovery-in-a-distributed-setting" rel="nofollow">https://docs.dbos.dev/production/workflow-recovery#recovery-...</a><p>>When self-hosting in a distributed setting without Conductor, it is important to manage workflow recovery so that when an executor crashes, restarts, or is shut down, its workflows are recovered. You should assign each executor running a DBOS application an executor ID through DBOS configuration. Each workflow is tagged with the ID of the executor that started it. When an application with an executor ID restarts, it only recovers pending workflows assigned to that executor ID.<p><a href="https://docs.dbos.dev/production/hosting-conductor" rel="nofollow">https://docs.dbos.dev/production/hosting-conductor</a><p>> Self-hosted Conductor is released under a proprietary license. Self-hosting Conductor for commercial or production use requires a paid license key.</p>
]]></description><pubDate>Fri, 01 May 2026 01:46:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=47970487</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=47970487</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47970487</guid></item><item><title><![CDATA[New comment by farsa in "Async Python Is Secretly Deterministic"]]></title><description><![CDATA[
<p>Well, in my early days programming python I made a lot(!!) of code assuming non-concurrent execution, but some of that code will break in the future with GIL removal. Hopefully the Python devs keep these important changes as opt-ins.</p>
]]></description><pubDate>Fri, 03 Apr 2026 21:05:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=47632286</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=47632286</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47632286</guid></item><item><title><![CDATA[New comment by farsa in "Tell HN: I'm 60 years old. Claude Code has re-ignited a passion"]]></title><description><![CDATA[
<p>I expect to have at least 15 more years in the workforce and I hate that I have to live through this "revolution". I worry about what will be final balance of lives improved vs lives worsened.</p>
]]></description><pubDate>Sat, 07 Mar 2026 04:11:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=47284407</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=47284407</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47284407</guid></item><item><title><![CDATA[New comment by farsa in "Show HN: PgDog – Scale Postgres without changing the app"]]></title><description><![CDATA[
<p>Congrats on the progress!
What is the behavior of PgDoc if it receives some sort of query it can't currently handle properly? Is there a linter/static analysis tool I can use to evaluate if my query will work?</p>
]]></description><pubDate>Tue, 24 Feb 2026 00:15:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=47131018</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=47131018</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47131018</guid></item><item><title><![CDATA[New comment by farsa in "Apache Arrow is 10 years old"]]></title><description><![CDATA[
<p>Storage getting cheaper did not really reach the cloud providers and for self-hosting it has recently gotten even more expensive due to AI bs.</p>
]]></description><pubDate>Fri, 13 Feb 2026 00:16:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=46997191</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=46997191</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46997191</guid></item><item><title><![CDATA[New comment by farsa in "Bloom filters are good for search that does not scale"]]></title><description><![CDATA[
<p>The distinction is more clear when indexing actual text and applying tokenization. A "typical" index on a database column goes like "column(value => rows)". When people mention inverted indexes its usually in the context of full text search, where "column value" usually goes through tokenization and you build an index for all N tokens of a column "column:(token 1 => rows)", "column:(token 2 => rows)",... "column:(token N => rows)".</p>
]]></description><pubDate>Tue, 04 Nov 2025 23:37:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=45817187</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=45817187</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45817187</guid></item><item><title><![CDATA[New comment by farsa in "How we replaced Elasticsearch and MongoDB with Rust and RocksDB"]]></title><description><![CDATA[
<p>What was your experience like putting such thing together?</p>
]]></description><pubDate>Sun, 10 Aug 2025 00:48:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=44851817</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=44851817</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44851817</guid></item><item><title><![CDATA[New comment by farsa in "How we replaced Elasticsearch and MongoDB with Rust and RocksDB"]]></title><description><![CDATA[
<p>Not the person you have asked but at work (we are a CRM platform) we allow our clients to arbitrarily query their userbase to find matching users for marketing campaigns (email, sms, whatsapp). These campaigns can some times target a few hundred thousand people. We are on a really ancient version of ES, but it sucks at this job in terms of throughput. Some experimenting with bigquery indicates it is so much better at mass exporting.</p>
]]></description><pubDate>Sun, 10 Aug 2025 00:45:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=44851804</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=44851804</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44851804</guid></item><item><title><![CDATA[New comment by farsa in "Should you ditch Spark for DuckDB or Polars?"]]></title><description><![CDATA[
<p>Hey, you have some silly thing rendered at your product's landing page chewing CPU.</p>
]]></description><pubDate>Sun, 15 Dec 2024 22:07:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=42426311</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=42426311</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42426311</guid></item><item><title><![CDATA[New comment by farsa in "Full text search over Postgres: Elasticsearch vs. alternatives"]]></title><description><![CDATA[
<p>It's still in technical preview.</p>
]]></description><pubDate>Tue, 06 Aug 2024 23:58:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=41176836</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=41176836</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41176836</guid></item><item><title><![CDATA[New comment by farsa in "Ways to capture changes in Postgres"]]></title><description><![CDATA[
<p>It's not exactly simple as it involves some postgres specific knowledge, but you can make it reliable when working with transaction ids (see <a href="https://event-driven.io/en/ordering_in_postgres_outbox/" rel="nofollow noreferrer">https://event-driven.io/en/ordering_in_postgres_outbox/</a>).</p>
]]></description><pubDate>Fri, 22 Sep 2023 15:29:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=37613339</link><dc:creator>farsa</dc:creator><comments>https://news.ycombinator.com/item?id=37613339</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37613339</guid></item></channel></rss>