I was initially happy about this, but the more I think about it the more I'm on the fence. I'm just starting to get in to using Parse this week, so can someone with a little more experience give some thoughts?<p>It seems to me that a smaller app would be more likely to occasionally burst over 30 req/s than go over 1m req/mo. Is it as simple as retrying requests that return error code 155 (per the FAQ)?<p><a href="https://parse.com/plans/faq/" rel="nofollow">https://parse.com/plans/faq/</a>
I feel the new price structure is a welcome change. Regarding the req/s limit I also at first felt I would be able to hit it easily, but the more I've calculated it I can see I will be nowhere near that limit.<p>I've made an native iOS app to use the Data Browser from the phone. It's something I think a lot of Parse users can benefit from using, I wish they'd informed about it in their presentation!
This makes a "fan-out" model for any feed-type app pretty difficult. For example in an app with friends or followers, when a user posts something the app would perform inserts to add the post into the followers/friends feed tables. It's very bursty, and would be very expensive with this new pricing scheme.