Hacker News Reader

Comment by owensbla | Hacker News Reader

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?

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)?

https://parse.com/plans/faq/

View on HN

I'm doing about 15m/mo and my peak req/sec so far is 24 which looks out of the normal cycle by about 2.5 req/sec. We can double our limit for a lot less than what we're paying monthly now so this is a welcome change for us. I would think retrying 155 responses would work ok for us while refactoring to reduce calls. I think the new offline data store ability will help with reducing requests.

I've been using Parse for a few years now and have always been happy with them. Their service offerings have been growing right along with my needs so it's been great. I'm happily welcoming this announcement.

That's good to know, appreciate the insight!

Thanks janj! What type of app do you use? Is it gaming-heavy, text-heavy, etc?

It's a social app for people who vacation on cruises. You can create a profile, store cruises you've been on or are going on in the future, communicate with fellow cruisers, submit pics, reviews, etc. All of it is done through Parse. We also utilize Parse's Cloud Code to send data to the parent company's web site. I'm sure we're not using Parse to its full potential but we're a small group right now.

Reply on news.ycombinator.com