This isn't a purely technical pros/cons, but still a good way of looking at them both:
- They are both well backed (Heroku by Salesforce money/profits, Parse by great investors), have awesome founders, talented employees, and are both YC companies.
- Parse is pretty much 100% mobile focused. This is their bread and butter.
- Heroku is Polyglot and spans dozens of platforms on multiple OS's, with no real focus.
I think this comes down to where you run the rest of your stack, how tightly you want things integrated, and which service is the easiest to use and most reliable. Is mobile 99% of what you do? Parse is probably the best choice. Is mobile 25% of your business and you're already using Heroku for everything else? I could go either way here. We use Heroku and AWS to drive 100% of our platform, but we're also not mobile (yet). I personally know the Parse guys and they are outstanding at what they do and growing at a phenomenal rate, so when we do dive into mobile I'll likely be giving them a shot first.
It seems Parse offers many nice features in addition to transparent-ish "cloud" persistence, e.g Push notifications, etc.
Heroku's approach is really interesting. The idea of building a db model from the CoreData model is (I think) really elegant, but:
- I'll also need to write an Android app
- AFIncrementalStore is more generic but Parse's specialized classes seem more "plug-and-play".
ymmv but we had a lot of problems with extreme slowness and downtime when using parse, it made development a bear and we were only using it for some testing. We wouldn't use it in production after our experience.
I think mileage definitely varies! I use Parse on a large app in production (100,000+ active users) and haven't experienced any downtime or slowness. Although perhaps my use-case is different to yours. You should try getting in touch with the Parse guys, I've found them very helpful and responsive. Just thought I'd offer the other side of the coin.
- They are both well backed (Heroku by Salesforce money/profits, Parse by great investors), have awesome founders, talented employees, and are both YC companies.
- Parse is pretty much 100% mobile focused. This is their bread and butter.
- Heroku is Polyglot and spans dozens of platforms on multiple OS's, with no real focus.
I think this comes down to where you run the rest of your stack, how tightly you want things integrated, and which service is the easiest to use and most reliable. Is mobile 99% of what you do? Parse is probably the best choice. Is mobile 25% of your business and you're already using Heroku for everything else? I could go either way here. We use Heroku and AWS to drive 100% of our platform, but we're also not mobile (yet). I personally know the Parse guys and they are outstanding at what they do and growing at a phenomenal rate, so when we do dive into mobile I'll likely be giving them a shot first.