We are a startup, working on ... well ... another instant messaging and sharing app!! The goal is of course to reach millions of users.
From a time to launch perspective we are wondering if it is at all a good idea to use BaaS services like parse/StacKMob/PubNub. While we are aware of most of the pros and cons of using a BaaS, our main worries with BaaS are high costs at a later stage when users multiply, vendor lock-in. Some things we would love some experienced hackers to throw light on are:
- Any idea on costs of BaaS once one moves into the enterprise usage range with millions of API calls per day
- can one launch with a BaaS backend, and then as the app is gaining traction, build out and switch to a custom solution? is this practically feasible?
- if above (switch to custom solution) is feasible then any specific advice on what one must keep in mind while architecting the app, and any recommendations on a BaaS provider that is easier to switch over from
- any other insight if you think this is a complete no no
cheers
Ani
From a time to launch perspective we are wondering if it is at all a good idea to use BaaS services like parse/StacKMob/PubNub. While we are aware of most of the pros and cons of using a BaaS, our main worries with BaaS are high costs at a later stage when users multiply, vendor lock-in. Some things we would love some experienced hackers to throw light on are:
- Any idea on costs of BaaS once one moves into the enterprise usage range with millions of API calls per day
- can one launch with a BaaS backend, and then as the app is gaining traction, build out and switch to a custom solution? is this practically feasible?
- if above (switch to custom solution) is feasible then any specific advice on what one must keep in mind while architecting the app, and any recommendations on a BaaS provider that is easier to switch over from
- any other insight if you think this is a complete no no
cheers Ani