3 ms·
> The official solution is to fan out to multiple streams Not anymore. Enhanced fanout allows up to 20 consumers, doesn't count against read limits and has low
by phamilton 7y ago
> The official solution is to fan out to multiple streams
Not anymore. Enhanced fanout allows up to 20 consumers, doesn't count against read limits and has lower latency than polling.
> It's very, very easy for provisioned capacity to be more expensive than on-demand.
Reserved capacity will beat on-demand pretty handily, even with massive overprovisioning. Assuming a 50% target and a 16 hour daily duty cycle, reserved provisioned is 20% the cost of running on-demand.
- plexicle 7y ago> Reserved capacity will beat on-demand pretty handily, even with massive overprovisioning. Assuming a 50% target and a 16 hour daily duty cycle, reserved provisioned is 20% the cost of running on-demand. I don't have the math on hand at the moment.. but switching to on-demand for us resulted in HUGE savings. We weren't overprovisioned either, but we were kind of spiky (in fact we were underprovisioned for a lot of the day).
- jbergknoff 7y agoThanks, I misspoke about fanning out to multiple streams. Dedicated stream consumers are still a hack. They're also expensive and have limitations as Lambda event sources. Kinesis is a service that needs to be used very carefully. It's riddled with landmines for cost and performance. Regarding Dynamo: I'll echo plexicle's experience that switching to on-demand was an immense cost savings (these were tables that were not being used often, many of them in dev environments).