<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: Lapapapaja</title><link>https://news.ycombinator.com/user?id=Lapapapaja</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 10 Apr 2026 12:57:15 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Lapapapaja" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Lapapapaja in "Distributed Transactions at Scale in Amazon DynamoDB (2023)"]]></title><description><![CDATA[
<p>> I still lean into events & eventual consistency to manage state across the various nodes.<p>You can get really far with a RDMS before event sourcing etc is needed, the benefit being both your dev and user experience are going to be much simpler and easier.<p>If you already know your problem domain and scaling concerns up front sure. But starting with a scalable pattern like this is a premature optimization otherwise and will just slow you down.</p>
]]></description><pubDate>Wed, 15 Jan 2025 13:35:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=42710562</link><dc:creator>Lapapapaja</dc:creator><comments>https://news.ycombinator.com/item?id=42710562</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42710562</guid></item></channel></rss>