[Interest] Moving from Parse

[Nuno Santos]

Jason,

What I really want to avoid is to manage my own servers. That takes me a lot of time. I want to focus myself on doing development and not server management. 

I also want that basic stuff such as users registration, registration emails, etc to be provided by the backend already, otherwise I would need to invest time in making my own.

Regards,

Nuno

> On 28 Mar 2016, at 20:55, Jason H <jhihn at gmx.com> wrote:
> 
> I'm not sure I see your problem. You're using Qt, you can use QJson* classes, QNAM, and interop with these without issue.
> I believe you can just use MongoDB, as a JS object store. I've not done that though, but that seems the path of most resistence. I personally just roll my own using Node/Express/Postgres (since the newer Prostgres has JSONB datatype)
>  
> Sent: Monday, March 28, 2016 at 2:12 PM
> From: "Nuno Santos" <nunosantos at imaginando.pt>
> To: interest <interest at qt-project.org>
> Subject: [Interest] Moving from Parse
> Hi,
>  
> Since Parse announced it’s shutdown I have been looking for a pain free and scaling solution.
>  
> The most difficult problem is to find a baas/daas that has a C++ client lib. All platforms out there only provide REST API as an alternative to iOS and Android libs.
>  
> Question: what are you people using for baas/daas of your Qt based applications? 
>  
> Thanks,
>  
> Regards
>  
> Nuno
> _______________________________________________ Interest mailing list Interest at qt-project.org http://lists.qt-project.org/mailman/listinfo/interest <http://lists.qt-project.org/mailman/listinfo/interest>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20160328/3ae7628a/attachment.html>