281–290 of 543 posts
Consider moving to Couchbase Mobile (http://developer.couchbase.com/mobile). Its an open source solution that allows you to build mobile applications that work online and offline.
With Couchbase Lite, you have the full power of a Couchbase database locally on the device. You can create, update, delete, query, sync and much, much more.
Separately, we developed an open-source Parse-compatible API server for Node/Express. https://github.com/ParsePlatform/parse-server This, along with the database migration tools released earlier, allow developers a full migration path to move from Parse hosted data + API to their own infrastructure. Over the weekend, I set up a website & app on a $5 DigitalOcean box running Parse and Mongo locally.
how long does the full migration and setting the digitical ocean box take to do? debating whether i should do that, or just start over with firebase
Earlier quoted context omitted.
sigh, I just made my first app on Parse and now I have to migrate to another BaaS. what do you recommend? Firebase? I dont' think running my own servers with Parse is viable as Parse won't be updated from now on while other BaaS will stay updated and keep improving
Firebase is good for small hackathon-like projects and it gets ugly when your DB grows. Not much optimizations you can do.
Earlier quoted context omitted.
We used Parse, and (contrary to your suggestion) it helped us get to market much slower and much more expensively . We experienced a hilarious amount of downtime, and hundreds of engineering hours that could have been spent developing features for our users or improving our services were spent working around fatal bugs in Parse, which were usually not manifesting on all instances, which made it very difficult for the…
Interesting. Sounds like Parse wasn't nearly as mature as they made themselves out to be. I'd have expected at least PaaS levels of stability—by, at the very least, pinning each client to a particular API version with guaranteed semantics until they choose to shift to making requests on higher-versioned equivalents of each API resource. A thought: if "Parse" had originally just been this open source Parse Server offe…
So, I would say, if Parse had been this Parse Server product from the start, that would have been a lot better! But there wasn't really any need for such a thing at my company. We had to use Parse for incestuous "YC alum" reasons---we did not have a technical need for it.
Earlier quoted context omitted.
If resource is the question, then I wonder how come they are sustaining WhatsApp? Its a zero-profit activity, the users chat amongst themselves, what does FB gain from that? I guess the parse resource traffic would be little compared to terabytes flowing through the WhatsApp every day.
you kidding?? Knowing what 200MM people are talking about and being able to display them "relevant" ads based upon it is priceless!!
And just when I was about to choose between Parse and Google's Firebase. Makes me wonder if Firebase will follow the same path through acquisition, seeming stability, followed by closing? As far as similar open-source systems, it seems like Mozilla's Kinto compares favorably to Parse after it's code is released: http://kinto.readthedocs.org/en/latest/overview.html There's a nice table there comparing the different se…
You can also look at Couchbase Mobile (http://developer.couchbase.com/mobile) that is an open source mobile database and provides full power of a Couchbase database locally on the device. You can create, update, delete, query, sync and much, much more. Couchbase server provides full querying capabilities using SQL-like syntax for your JSON documents.
I don't understand why Facebook never integrated Parse into its own datacenter infrastructure. As far as I can tell, Parse still hosts all of its infrastructure on EC2 (DNS lookups for every Parse service point to an EC2 IP address). Hosting on EC2 made sense when Parse was an independent company, but didn't they sell to Facebook so they could benefit from Facebook infrastructure? This seems like Facebook throwing in…
A few thought : 1/ parse wasn't a core service for facebook, nor a relevant source of a revenu AND their API wasn't standard. Those points combined made it very risky for people to use it. 2/ since they open sourced their API now, and the service was a paid service, there's a very high probability that someone will very soon create a 100% compatible PAAS. 3/ firebase will be next to shutdown. Not because they suck, b…
- Its an open source solution that allows you to build mobile applications that work online and offline.
- With Couchbase Lite, you have the full power of a Couchbase database locally on the device. You can create, update, delete, query, sync and much, much more.
- Couchbase Sync Gateway gives you everything you need to securely sync on-device Couchbase Lite with Couchbase Server in the cloud. -- Replication -- Authentication -- Access Control -- Data Routing
- Couchbase Server is a high performance, scalable, always-on NoSQL database in the cloud. Sub-millisecond, high-throughput reads and writes give you consistent high performance. Couchbase Server is easy to scale out, and supports topology changes with no downtime. Validation
Earlier quoted context omitted.
Did you check out CloudBoost.io? Its an open platform on Docker + also available as a managed service.
Can someone tell me why this was downvoted? I couldn't find anything wrong with cloudboost.io except for the absence of a Dockerfile in their dockerhub repo. [edit] Oh, because of spamming. Nevermind.