4 ms·
Can you explain this a little more? We've been investigating kafka v kinesis, and the severe restrictions on kinesis' API has been giving us pause. http://docs
by erichmond 12y ago
Can you explain this a little more? We've been investigating kafka v kinesis, and the severe restrictions on kinesis' API has been giving us pause.
http://docs.aws.amazon.com/kinesis/latest/dev/service-sizes-and-limits.html http://docs.aws.amazon.com/kinesis/latest/dev/service-sizes-...
- Rapzid 12y agoHi erichmond. I'm sorry if that was a bit off-the-cuff; I was simply pointing out the price equivalence of the resources. I can however make a SOLID suggestion that any time somebody sees resource limits on AWS that might hold them back they should get in touch with their account manager(or solutions architect, etc) to see what can be done. There are very few hard limits. Most of the soft-limits are to prevent people's bills from exploding. As far as the API itself though, as is usually the case you might need to get a bit creative to design around AWS imposed constraints due to their design decisions. It might end up not feasible, or not worth it, for your particular use case. But I believe it's at least worth investigating/discussing.