4 ms·
These are also great features. But what happens to that customer that one day realizes they need just "one more" feature - and that feature happens to require t
by nsxwolf 15y ago
These are also great features. But what happens to that customer that one day realizes they need just "one more" feature - and that feature happens to require they start running their own enterprise?
Not trying to be overly critical here, what you've built is very enabling for a lot of app creators. But it seems to me that any really successful client of yours will eventually outgrow your feature set and need to migrate to a custom solution.
At that point I don't know how you hold on to those customers without needing to build something like a Heroku.
- lacker 15y agoI don't know how you hold on to those customers without needing to build something like a Heroku. This is a good point. One convenient feature of the Parse platform is that it's located on EC2, so developers can run their own servers on Heroku or just EC2 itself with <2ms latency to Parse if they need to run any generic code. So we can let Heroku build Heroku, and just make Parse work really well in conjunction. I think right now we have reasonable solutions for this. We would like the solutions to be not just reasonable, but amazing. So there are a lot of other ideas we have to make this sort of development easier. We're working on it.
- olegp 15y agoHave you considered making or supporting a slimmed down open source version of Parse? That way developers could self host and extend as necessary. Having the option to self host would probably increase adoption of your core offering.
- lacker 15y agoWe're thinking about it. Some components would be easier than others to decouple from our scaling systems, so it's a tricky technical question.