This is the same stack I've been using for a project at work, I was exited to see the Parse SDK wrapper but apparently it's a thin one. In my current project I have attempted to create a wrapper completely Parse-agnostic in hopes to be able to switch to another provider my changing a little config, it does the basics for now, but I'd have to rewrite it as it's a little tied to this specific project.
I'm curious to hear if anyone has done a similar effort or is serious about starting.
Comments
This is the same stack I've been using for a project at work, I was exited to see the Parse SDK wrapper but apparently it's a thin one. In my current project I have attempted to create a wrapper completely Parse-agnostic in hopes to be able to switch to another provider my changing a little config, it does the basics for now, but I'd have to rewrite it as it's a little tied to this specific project.
I'm curious to hear if anyone has done a similar effort or is serious about starting.
I saw something similar here http://ericterpstra.com/2012/10/example-crud-app-starring-an...
But there is a big tradeoff for API user experience if you want to make it 'switchable' to another service.
Alternatively, for switching, there's this: https://github.com/stevegraham/parseport