Love that this feature finally released. I was a dev manager on DynamoDB years ago when we first started working on this. I left three years ago and had almost

Love that this feature finally released. I was a dev manager on DynamoDB years ago when we first started working on this. I left three years ago and had almost given up hope that this feature would see the light of day. The great thing about it is that it helps with spiky and sporadic workloads. In my current work I have a bunch of unit tests that hit a set of dynamodb tables. I have those tables provisioned at a 5 RCU and 5 WCU each. Multiply this by ten tables and I'm paying $25 per month. In the grand scheme of costs, this isn't much, but it's annoying and adds up. (One can argue that unit tests should be hitting a mock or a dynamodb local. That's true, but you also want some tests that actually hit the service.) On demand can be great for sporadic tests, for prototypes, for small personal projects, and for just messing around. There are also spiky non-customer-facing production scenarios that can benefit from On demand.