<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: zw17</title><link>https://news.ycombinator.com/user?id=zw17</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 11 Jun 2026 02:56:02 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=zw17" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by zw17 in "Show HN: HelixDB – A graph database built on object storage"]]></title><description><![CDATA[
<p>If your use case is OLAP based, please check it out PuppyGraph. It’s a graph query engine that sits on top of your Lakehouse (no ETL required). Our benchmark has shown consistently that 10-hop queries across billions of edges in <2 seconds. Our customers including some most data demanding companies like Coinbase, Datadog, Palo Alto Network, Netskope, AMD, etc.</p>
]]></description><pubDate>Wed, 10 Jun 2026 16:31:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=48478801</link><dc:creator>zw17</dc:creator><comments>https://news.ycombinator.com/item?id=48478801</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48478801</guid></item><item><title><![CDATA[New comment by zw17 in "What Is Graph Anomaly Detection"]]></title><description><![CDATA[
<p>Thank you so much for liking our blog! This is Zhenni, cofounder of PuppyGraph. Happy to answer any questions.</p>
]]></description><pubDate>Thu, 13 Nov 2025 15:27:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=45916011</link><dc:creator>zw17</dc:creator><comments>https://news.ycombinator.com/item?id=45916011</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45916011</guid></item><item><title><![CDATA[New comment by zw17 in "Migrating from AWS to Hetzner"]]></title><description><![CDATA[
<p>Just want to chime in. Zhenni, cofounder of PuppyGraph. We created the first graph query engine that can sit on top of your relational databases (think Postgres, Iceberg, Delta lake, etc.), and query your relational data as a graph using Cypher and Gremlin, without any ETL or a separate graphdb needed. It's much more lightweight and easy to spin up. Because we sit on top of column based storage and our compute engine is distributed, we can achieve subsecond query speed across 1 billion nodes. Please check it out!</p>
]]></description><pubDate>Fri, 17 Oct 2025 17:13:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=45619207</link><dc:creator>zw17</dc:creator><comments>https://news.ycombinator.com/item?id=45619207</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45619207</guid></item><item><title><![CDATA[New comment by zw17 in "SQL needed structure"]]></title><description><![CDATA[
<p>Interesting points here. I’ve found the “graph DB vs. relational DB” discussion usually gets framed as an either/or, but there’s a middle ground.<p>A lot of teams already have their data sitting in Postgres, Mongo, or a lakehouse. Spinning up a separate graph database just for traversals often means duplicating data, building pipelines, and keeping two systems in sync. That’s fine if you need deep graph algorithms, but for many workloads it’s overkill.<p>What some folks are exploring now is running graph queries directly on top of their existing data, without having to ETL into a dedicated graph DB. You still get multi-hop traversal and knowledge graph use cases, but avoid the “yet another database” tax.<p>So yeah...graph databases are great, but they’re not the only way to model or query graphs anymore.</p>
]]></description><pubDate>Sat, 06 Sep 2025 02:17:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=45146007</link><dc:creator>zw17</dc:creator><comments>https://news.ycombinator.com/item?id=45146007</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45146007</guid></item><item><title><![CDATA[How Wiz Crushed Lacework: A Data Infrastructure Perspective]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.puppygraph.com/blog/how-wiz-crushed-lacework-a-data-infrastructure-perspective">https://www.puppygraph.com/blog/how-wiz-crushed-lacework-a-data-infrastructure-perspective</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44776975">https://news.ycombinator.com/item?id=44776975</a></p>
<p>Points: 4</p>
<p># Comments: 1</p>
]]></description><pubDate>Sun, 03 Aug 2025 14:54:38 +0000</pubDate><link>https://www.puppygraph.com/blog/how-wiz-crushed-lacework-a-data-infrastructure-perspective</link><dc:creator>zw17</dc:creator><comments>https://news.ycombinator.com/item?id=44776975</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44776975</guid></item><item><title><![CDATA[New comment by zw17 in "Ursa: A leaderless, object storage–based alternative to Kafka"]]></title><description><![CDATA[
<p>Congrats on the launch! This is Zhenni from PuppyGraph. Shameless plug - We recently supported Ursa and here is the joint blog to showcase how to integrate Ursa engine with PuppyGraph to enable real-time graph analytics for a financial service use case with data stored in a lake house (not graphDB): <a href="https://streamnative.io/blog/integrating-streamnatives-ursa-engine-with-puppygraph-for-real-time-graph-analysis" rel="nofollow">https://streamnative.io/blog/integrating-streamnatives-ursa-...</a></p>
]]></description><pubDate>Thu, 31 Jul 2025 17:53:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=44748225</link><dc:creator>zw17</dc:creator><comments>https://news.ycombinator.com/item?id=44748225</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44748225</guid></item></channel></rss>