271–280 of 297 posts
Earlier quoted context omitted.
I'm also confused. "API as a service" sounds to me like "service as a service"... ok, it's a service, but what does it do ?
And if I download the open source code, and run it on my own server, is it a service as a service as whatever-the-opposite-of-a-service is? I'm confused...
Earlier quoted context omitted.
Something I've been wondering is would you recommend using the open source Parse server for new code or is it more targeted towards projects that were already using the Parse API?
It's geared towards legacy. I have used parse in 3 different projects (none of that was my choice, these were existing projects I had to take over) and I would NEVER recommend it for new projects. The way everyone seems to use it, in my experience, is giving the client credentials to manipulate the full database which is absolutely insane. Obviously this is not good practice but every single parse project I've gotten…
Not to disagree with your overall assessment. I'm generally wary of these swiss-knife frameworks - they're written for a particular use case in mind, and if your project doesn't fit that, you may go through contortions to get things working smoothly.
Earlier quoted context omitted.
So many posts on HN are like this, assuming that every obscure webservice is common knowledge. "Jabberwocky has reached version 1.1! Performance increased by 30%, users must migrate from 1.0 by the 12th. Use Jabberwocky in your business now! New users get a free trial!" OK that's nice but what tf is it and why should I care?
Yesterday I built a 100M user social network using Jabberwocky. It took me just 25 minutes, bro, and now I've retired to my own private Caribbean island.
Earlier quoted context omitted.
> Parse was an API as a service. The idea being that you don't need your own servers and parse would provide API, database, push messaging and so on. I'm still unclear. It's some sort of hosted database+services?
I'm also confused. "API as a service" sounds to me like "service as a service"... ok, it's a service, but what does it do ?
perhaps this http://rawrmaan.com/why-parse-failed/ might be a better explanation ?
So the alternative options are: - pouchDB - https://github.com/pouchdb/pouchdb - RxDB - https://github.com/pubkey/rxdb - gunDB - https://github.com/amark/gun - horzion - https://github.com/rethinkdb/horizon - firebase - https://firebase.google.com/
Kind of strange that you just threw in RxDB (your own creation?) and GunDB (which is easily torn apart as snakeoil whenever it appears on HN) along with the rest of them.
A little Parse trivia a gathered from talking to (very capable) Parse engineers that now work at FB: - Still the world's largest MongoDB user - Had 1M apps, largest one with 40M users - Server was Rails at first (24 threads max. concurrency), later rewritten in Go - >40 MongoDB Replica Sets with 3 nodes each. Storage Engine: RockDB (MongoRocks). No sharding (DB-to-replica-set-mapping). Only instance storage SSDs, no…
Even with higher levels of "consistency" Mongo is still unsafe [1]. [1]: https://aphyr.com/posts/322-jepsen-mongodb-stale-reads
A little Parse trivia a gathered from talking to (very capable) Parse engineers that now work at FB: - Still the world's largest MongoDB user - Had 1M apps, largest one with 40M users - Server was Rails at first (24 threads max. concurrency), later rewritten in Go - >40 MongoDB Replica Sets with 3 nodes each. Storage Engine: RockDB (MongoRocks). No sharding (DB-to-replica-set-mapping). Only instance storage SSDs, no…
> which Parse only was after it had already failed You just listed some pretty impressive metrics, Parse was acquired for $85M and yet, you still think that Parse failed? I'm curious what you would call a success.
From a standpoint of traction it was no failure. A lot of developers liked it for a good reason. However, the pricing model and the lack of performance guarantees lead Parse to being used for prototype stuff in the free-tier mainly. I think, if they had a little more trust in the capabilities of developers to know what they are doing, the service might still be alive.
Quick... everyone run to www.graph.cool !! It's parse but for GraphQL!
The way you phrased it almost seem sarcastic in the context of this thread, although i think you are actually recommending them :) They offer a interesting product but i think at this moment it has the exact same problem that Parse had (my other comment in this thread), you don't have access to the raw data, hope they will do that in the future (provide direct access to the source database), it will certainly be a mo…
I'd be very keen on hearing your experience getting started building something on Graphcool!
Quick... everyone run to www.graph.cool !! It's parse but for GraphQL!
In general GraphQL provides many advantages over a traditional REST like API provided by most BaaS. It frees you from the need for proprietary SDKs and reduces vendor lock-in.
Here is a quick way how you can get started: https://www.graph.cool/docs/quickstart