<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael Tsibelman on Medium]]></title>
        <description><![CDATA[Stories by Michael Tsibelman on Medium]]></description>
        <link>https://medium.com/@tsibelman?source=rss-10bf302aecd0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eA4lIPdZWbHW-JnT.</url>
            <title>Stories by Michael Tsibelman on Medium</title>
            <link>https://medium.com/@tsibelman?source=rss-10bf302aecd0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:02:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tsibelman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[DynamoDB pricing in simple terms]]></title>
            <link>https://medium.com/@tsibelman/dynamodb-pricing-in-simple-terms-c0c54ad7d18b?source=rss-10bf302aecd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0c54ad7d18b</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[dynamodb]]></category>
            <dc:creator><![CDATA[Michael Tsibelman]]></dc:creator>
            <pubDate>Fri, 18 Jan 2019 18:50:01 GMT</pubDate>
            <atom:updated>2019-01-18T18:50:01.257Z</atom:updated>
            <content:encoded><![CDATA[<p>I was doing some analysis on DynamoDB pricing and wanted to share it with you all.</p><p>DynamoDB has two modes of billing: the first is <strong>capacity</strong> based mode (RCU/WCU), the second one is <strong>pay-per-request</strong> payment mode.</p><p>These modes have very different pricing mechanisms, and it is important to understand the differences.</p><p><strong>Provisioned Capacity</strong></p><p>In this mode, the price based on your desired throughput in KB/s, RCU (read capacity unit) stands for 4KB/sec and WCU (write capacity unit) stands for 1KB/sec.</p><p>So when you think about how much WCU/RCU your application requires, you need to understand what it is your maximum throughput at any given time (your highest spike) and not how much traffic you have overall.</p><p>To demonstrate this difference see the two graphs below. In both of them we need to write 5KB of data but in the left graph we have a peak where all 5KB are written at once, and in the right-hand side, we have an even distribution of 1KB/s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/0*ZIHdoiB31qwBmDOW.png" /></figure><p>To accommodate the first scenario you will need to buy 5 WCU and for a right-hand scenario you need just 1 WCU, so it will be five times cheaper.</p><p>This leads to situations where even low traffic application needs to overcommit on WCUs to accommodate occasional peaks in traffic.</p><p>The payment has a resolution of one hour, so if your application has predictive daily variability, it’s possible to write a smart scheduling mechanism to adjust your WCU capacity according to the time of day to accommodate for this variability.</p><p>AWS provides some rudimentary auto scheduling implementation that can adjust your capacity based on previous traffic patterns, but it’s not very responsive, and I don’t recommend relying on it for more critical applications.</p><p>In this mode tables and their indexes can have a different capacity so it is possible to have a less expensive bill for some operations that you are ok with doing over more extended periods.</p><p><strong>On-Demand</strong> <strong>pay per request mode</strong></p><p>This is a simpler model to understand, in this mode throughput is not important at all, your bill is based on the total numbers of requests instead. So for the graphs above you will pay the same for both scenarios. And if your DB not used at all, you pay zero, that is very useful for testing and dev environments.</p><p>So if you have situations where the total number of requests is relatively small, but variance in throughput is high, it will be way cheaper to use the per request mode.</p><p>Below you can find a small calculator were you can play with the numbers:</p><p><a href="https://docs.google.com/spreadsheets/d/10Y_cMZF3JAeH5z2F7qsVVAw3qSEGL5cOQ_sFNOq2kPk/edit?usp=sharing">https://docs.google.com/spreadsheets/d/10Y_cMZF3JAeH5z2F7qsVVAw3qSEGL5cOQ_sFNOq2kPk/edit?usp=sharing</a></p><p>If you have any question, please feel free to ask, DynamoDB it’s an overly complex subject in my opinion, and I am hoping I didn’t miss anything, so please tell me if you found something you believe isn’t accurate</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0c54ad7d18b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>