亚马逊DynamoDB不提供inbuild功能，自动调节吞吐基于动态负载。 它提供的API来增加或减少产量。客户正在收费调配阅读及功放小时计算;写吞吐量。

Amazon DynamoDB doesn’t provide inbuild capabilities to auto tune throughput based on Dynamic Load. It provide API to increase or Decrease throughput. Customers are being charges hourly basis for provisioned read & write throughput.

有哪些不同的方式来改变吞吐量dynamodb，实现成本节约的好处？

What are the different ways to alter throughput of dynamodb and achieve cost saving benefits ?

推荐答案

从克里斯的回答是一个准确的答案。只是为了使用DynamoDB以往的经验补充几点...

The answer from Chris is an accurate answer. Just to add a few points from prior experience using DynamoDB …

与DynamoDB的情况与EC2不同。弹性计算服务具有直接支持通过亚马逊Web服务的API，允许你计划如何根据一些逻辑，放大或缩小等尽可能多的需求是如何存在。你的程序通过定义一个监控阈值和自动触发创建实例或删除在一组。

The situation with DynamoDB is different from EC2. The elastic compute service has an API supported directly as a web service by Amazon to allow you to program how to scale up or down according some logic such as how much demand exists. You program this by defining a monitoring threshold and automatically triggering creation or deletion of instances in a group.

数据服务器不会以同样的方式工作，触发调整的能力。但DynamoDB的容量是非常灵活的，并且可以被控制为克里斯指出。该API提供，这是不够好，使一次性更改。从控制台或等效的手动更改。

Data servers do not work in the same way with triggers to adjust their capacity. But the capacity of DynamoDB is very flexible and may be controlled as Chris has pointed out. The API to provide this is good enough to make one off changes. Or equivalent manual changes from the console.

在不同的语言绑定程序中创建和更新操作与DynamoDB是在这里...

The different language bindings to program create and update actions with DynamoDB is here …

   http://docs.aws.amazon.com/cli/latest/reference/dynamodb/index.html

修改能力的重要的操作就是在这里...

The important operation to modify capacity is here …

   http://docs.aws.amazon.com/cli/latest/reference/dynamodb/update-table.html

所以，这使您能够在ProvisionedThroughput的ReadCapacityUnits或WriteCapacityUnits的增加或减少的能力。

So this gives you the ability to make an increase or decrease in the ReadCapacityUnits or WriteCapacityUnits of ProvisionedThroughput.

这是罚款的predicted或一次性的改变。但是，这是不一样的事情作为一个灵活的工具，让你自动触发的变化。

Which is fine for a predicted or one-off change. But that is not the same thing as a flexibility tool to allow you to trigger the change automatically.

编程，你最有可能想要做的是调整运力应对利用率改变在preceding时间间隔。特别是，您可能需要迅速扩展以应对需求激增通过定义一个适当的时隙和下限和上限阈值触发。

Programmatically, what you are most likely to want to do is to adjust capacity in response to change in utilization in the preceding time interval. In particular you may need to scale up rapidly in response to a surge in demand by defining an appropriate time slot and a lower and upper threshold to trigger.

一个更完整的解决方案来实现，这是这里描述...

A more complete solution to achieve this is described here …

  https://aws.amazon.com/blogs/aws/auto-scale-dynamodb-with-dynamic-dynamodb/

将溶液通过Sebastian谢达尔格伦保持，并且可以与所有的指令来发现在...

The solution is maintained by Sebastian Dahlgren and may be found with all instructions at …

  https://github.com/sebdah/dynamic-dynamodb

我看到现在的版本是1.18.5，比我上次用它更近一些。

I see that the current release is 1.18.5 which is more recent than when I last used it.

从早期版本判断，简单的通过一个dynamodb.conf属性样式文件...

Judging from earlier releases it is simple to configure by means of a dynamodb.conf properties style file …

具有提供的凭据和地区，最关键的设置是

Having provided credentials and region, the most crucial settings are

这个信息是最新的？

那么，如果你看一下 http://aws.amazon.com/new/ 你会看到只有一个额外的近更改影响DynamoDB会影响存储的文件。动态DynamoDB的条目是上次发布的条目处理缩放动作。因此，这是在这个时候最好保持DynamoDB自动缩放功能。

Well if you look at http://aws.amazon.com/new/ you will see just one additional recent change affecting DynamoDB which affects the documents stored. The entry for Dynamic DynamoDB is the last published entry dealing with scaling actions. So this is the best maintained DynamoDB automatic scaling capability at this time.