Did I do the math correctly? No. But the genereal idea is in place.
Dear Amazon SQS Developers,
We wanted to let you know about some changes we are making to Amazon SQS, based on customer feedback and watching the way customers are using the service. One thing we’ve heard consistently is that customers want to be able to use SQS along with our other services (e.g. Amazon EC2, Amazon S3), but need SQS to be less expensive for this to be more feasible. We looked at our architecture and feature set, and found a way to make a few, targeted changes, by deprecating a few infrequently used requests, which allow us to operate the service much more efficiently. Simultaneously, we are introducing a new pricing structure that replaces the previous per-messages-sent charge ($0.10/1,000 messages) with a new per-request fee ($0.01/10,000 requests, including all Amazon SQS operations). The net result is that the new pricing will result in significantly lower charges for most developers being billed for SQS.
Yeah, I’d say that’s pretty significant. Nice!
More details @ the AWS/SQS page.
Do note that they changed from per-message to per-request. Before, if there was no message, you didn't pay (if I recall correctly). Now, you pay even if there's no message. Having said that, it's still a gigantic drop for busy users.
@petrilli,
>> Do note that they changed from per-message to per-request. Before, if there was no message, you didn't pay (if I recall correctly).
It's going to take a lot of requests to an empty queue to make up the difference! :D
>> Now, you pay even if there's no message. Having said that, it's still a gigantic drop for busy users.
Oh, it's huge! I hadn't even considered SQS because the cost seemed to high for the benefit provided. But that's most definitely changed.
Actually, it's only a 99.99% price drop, but either way that's fantastic!
It's not 10.000%. If it's 100 times cheaper, then it's only a 99% drop. 100% drop would mean that it's free now. Although it would work with 10.000% if Amazon would increase the price back how it was before...
@Ryan, tamole,
Thanks! fixed.