iphone - Own Backend vs BaaS -

I am trying to make a decision between two development firms. Wants to go with a parse, while the second wants to make the backend, I would like to get feedback and reasons, because using backbend or using bass like dice, Skeakbob is better in scalability and performance.

For example, we use a highly used app of SnapChat that manages millions of users and data requests if a newly created app Registration of user and what data is to take a large increase in requests. Will backend be able to handle this? Do I want to fix users immediately after the increase?

Parse.com gives a lot of value for very little capital investment, with Baas, All the terrible details of the management of the infrastructure are hidden; innumerable buses of deployments, system capacity issues, system availability, system security, database administration and other functions just move away using a good Baas. For example, Parse.com uses Amazon Web Services and Luvstil load balancing so that more efficiency is added dynamically due to increased usage in the system. This capacity is Nirvana of management.

Parse.com is a special type of bass. The purpose of Parse.com should be the light-weight back-end for the mobile app. I believe Parse.com is a very good mobile backend-a-a-service ().

At that time, there are times when Parse.com is not the right solution. Measure the number of users for the app and the number of HTTP requests and average users will be sent in one day. Parse.com fee by number of transactions Transaction can result in more cost to the app owner, for example, if there are 4,500 users, then send 125 requests per day to Parse.com, you already see 16,850,000 requests every 30 days Are there. Parse.com provides a high level service called Pars Enterprise, details about this plan are not published.

The services provided by a bass / MBASS save more time and energy from the application developer, but some obstacles are imposed. For example, Parse.com's response time may be very slow for your needs, unless you upgrade to your enterprise plan, you have no control over the response time. Currently you have no control over hosting your app (Pars App is currently out of Amazon's data centers in Virginia).

I see Baas providers do not provide quality service metrics, even if they have done so, there is no content agreement that the matrix will be meaningful.

An application is a good candidate for MBAAS if:

1. This is simple or application logic can run completely on the customer (phone, tablet ...)
2. It is impossible to assess the number of users or the number of users may be larger.
3. You do not want to make large capital investments.
4. You do not want to hire infrastructure experts to handle capacity / security / data / recovery / network engineering.
5. Your application does not require strict response time.

   The best use of a pars is the iPhone Developer, which wrote a game and needs to collect the user's high score, but knows nothing about the servers, he said, complicated See applications that are using pars such as pars. Can you imagine your application in that portfolio or is it very different from this app?

   Even if no bass is the right solution, even then can be a loop or IASS. Look at Rackspace and AWS At this day and age, it is difficult to justify buying hardware and running data centers.