CODEWITHSUNDEEP
parse-platform
Jiew Meng
Jiew Meng

Reputation: 88207

Parse: Any "backend" actually needed?

I am reading up about Parse. It seems like to me that the main benefit is removing the need for a backend. However, I am starting to wonder if this is a good thing.

Assume I need an iOS and Android app. I imagine they both start developing models in the frontend. But isit this a problem if they both store data differently? Or maybe validate/process differently? Lets say there is a document to sync such decisions. Isn't it more work that each platform will do the same thing again?

Lets say to rectify this, I start developing APIs in cloud code for this. Am I not back to square one? It becomes similar to just building APIs with the usual tools like Express/Rails?

Maybe I am understanding it wrong?

Upvotes: 0

Views: 66

Answers (1)

Wain
Wain

Reputation: 119031

Parse removes the need for a specifically hosted back end in a lot of cases. That doesn't mean you shouldn't use cloud code to provide standard processing capability, security, privacy, etc for your platform. Parse also can't handle everything (like systems that store a lot of binary data). You need to consider what your system is and how you want it to operate. Putting common logic on a server and minimising the work done by clients of the system is a good plan, parse can help with that in a lot of cases. It also helps by offering other add-ons like push notification, email distribution, social login handling...

Upvotes: 1

Related Questions