We built a new DynamoDB cost analyzer that helps developers understand what their workloads will really cost DynamoDB costs can blindside you. Teams regularly face “bill shock”: that sinking feeling when you look at a shockingly high bill and realize that you haven’t paid enough attention to your usage, especially with on-demand pricing. Provisioned capacity brings a different risk: performance. If you can’t accurately predict capacity or your math is off, requests get throttled. It’s a delicate balancing act. Although , វាត្រូវបានបាត់បន្ថយទំហំនៃការធ្វើដំណើរពិភពលោកពិតប្រាកដ (ដូចជាការធ្វើដំណើរធ្លាក់ផ្អែកឬគំរូការចូលដំណើរការមិនត្រឹមត្រូវឬការប្រើថ្នាំទូទាំងពិភពលោកឬការកាត់បន្ថយ). AWS ផ្តល់នូវកំណត់តម្លៃ DynamoDB យើងចង់មានអ្វីដែលមានប្រសិទ្ធិភាពជាងមុន។ យើងចង់មានអ្វីដែលមានប្រសិទ្ធិភាពជាងមុនដើម្បីជួយក្រុមហ៊ុនរបស់យើងក្នុងការរៀបចំនៃការ . So we built a new DynamoDB cost calculator that helps developers understand what their workloads will really cost. Although we designed it for teams comparing DynamoDB with ScyllaDB, we believe it’s useful for anyone looking to more accurately estimate their DynamoDB costs, for any reason. You can see the live version at: ScyllaDB as a DynamoDB alternative calculator.scylladb.com ដូច្នេះយើងបានបង្កើតវា We wanted to build something that would work client side, without the need for any server components. It’s a simple JavaScript single page application that we currently host on GitHub pages. If you want to check out the source code, feel free to take a look at https://github.com/scylladb/calculator ដូច្នេះ, ដើម្បីធ្វើការជាមួយឧទាហរណ៍នៅលើ was a bit of a nightmare, and when you “show calculations,” you get these walls of text: https://calculator.aws/ I was tempted to take a shorter approach, like: Monthly WCU Cost = WCUs × Price_per_WCU_per_hour × 730 hours/month But every time I simplified this, I found it harder to get parity between what I calculated and the final price in AWS’s calculation. Sometimes the difference was due to rounding, other times it was due to the mixture of reserved + provision capacity, and so on. So to make it easier (for me) to debug, I faithfully followed their calculations line by line and tried to replicate this in my own rather ugly function: https://github.com/scylladb/calculator/blob/main/src/calculator.js I may still refactor this into smaller functions. But for now, I wanted to get parity between theirs and ours. You’ll see that there are also some end-to-end tests for these calculations — I use those to test for a bunch of different configurations. I will probably expand on these in time as well. So that gets the job done for On Demand, Provisioned (and Reserved) capacity models. If you’ve used AWS’s calculator, you know that you can’t specify things like a peak (or peak width) in On Demand. I’m not sure about their reasoning. I decided it would be easier for users to specify both the baseline and peak for reads and writes (respectively) in On Demand, much like Provisioned capacity. ខ្ញុំនឹងធ្វើប្រសើរជាងមុនជាមួយគំនូរជីវចល, ដូច្នេះមើលកញ្ចក់និងកញ្ចក់ធ្វើឱ្យខ្ញុំងាយស្រួលក្នុងការយល់ដឹង - ហើយខ្ញុំចង់បានសម្រាប់អ្នកផងដែរ។ អ្នកនឹងរកឃើញផងដែរថានៅពេលដែលអ្នកផ្លាស់ប្តូរដំណោះស្រាយដំណោះស្រាយ URL នឹងផ្លាស់ប្តូរទំហំដំណោះស្រាយដើម្បីបង្ហាញដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយដំណោះស្រាយ។ មានគំនិតច្នៃប្រឌិតផ្សេងទៀតដូចជាការរកឃើញតម្លៃពិតប្រាកដនៃ Global Tables និងការយល់ដឹងអំពីតម្លៃផលិតផលនៃអ្វីដូចជាការផ្លាស់ប្តូរបណ្តាញឬ DynamoDB Accelerator (DAX) ។ ទោះជាយ៉ាងណាក៏ដោយការពន្យល់ទាំងអស់ដែលមានកម្រិតខ្ពស់សម្រាប់ទំហំនេះ។ យើងនឹងនិយាយបន្ថែមទៀតអំពីវានៅក្នុងសាកលវិទ្យាល័យបណ្ដាញបន្ទាប់ (មើលកំណត់បន្ទាប់) ។ ដំណោះស្រាយដ៏ល្អគឺថាអ្នកអាចកំណត់តម្លៃទាំងនេះបន្ថែមទៀតទៅនឹងការធ្វើការរបស់អ្នក, ដូច្នេះពួកគេអាចជាការកំណត់តម្លៃធំទូលំទូលាយនៅពេលរចនាការប្រើប្រាស់ DynamoDB របស់អ្នក។ Explore “what if” scenarios for your own workloads Analyzing Costs in Real-World Scenarios The ultimate goal of all this tinkering and tuning is to help you explore various “what-if” scenarios from a DynamoDB cost perspective. To get started, we’re sharing the cost impacts of some of the more interesting DynamoDB user scenarios we’ve come across at ScyllaDB. លោក Gui និងខ្ញុំត្រឡប់មកវិញដើម្បីដោះស្រាយយ៉ាងទូលំទូលំទូលាយអំពីរបៀបដែលប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិនបើប្រសិន សូមមើល DynamoDB តម្លៃ ការហៅឥឡូវនេះ About Tim Koopmans Tim has had his hands in all forms of engineering for the past couple of decades with a penchant for reliability and security. In 2013 he founded Flood IO; a distributed performance testing platform. After it was acquired, he enjoyed scaling the product, business and team before moving on to other performance-related endeavors.
