<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: whsoul</title><link>https://news.ycombinator.com/user?id=whsoul</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 06 Sep 2026 13:34:59 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=whsoul" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by whsoul in "Ok, but Does It Scale?"]]></title><description><![CDATA[
<p>In my service, I have used one of distributed DB, vitess from beginning.
The problem was spending too many time for every time make table and shard key design to avoid placing a heavy load for DB with join, broadcast query, and so on.<p>I’d like to recommend If you are really need to scale out soon, your domain is difficult to separated, only use distributed DB.<p>It is true, distributed databases superior to many people technically,
But that’s not mean they are better in your service situation<p>I think it is better spend your time, separate domain architecture. Simply use DB.
Do not put unpredictable future off DB as past Oracle DB handle all.</p>
]]></description><pubDate>Fri, 04 Sep 2026 15:42:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=49566247</link><dc:creator>whsoul</dc:creator><comments>https://news.ycombinator.com/item?id=49566247</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49566247</guid></item></channel></rss>