20 ms·

Facebook is closing Parse

• gfosco 11y ago
  Separately, we developed an open-source Parse-compatible API server for Node/Express. https://github.com/ParsePlatform/parse-server 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.
  • theunquietone 11y ago
    Fosco, you are awesome and it was a pleasure working with you :)
    • jaboutboul 11y ago
      Hi Ashley! Thank you guys.
  • smrtinsert 11y ago
    The release of the server is an awesome gift to the community.
  • tbrock 11y ago
    Fosco, thank you for everything man.
  • vlucas 11y ago
    Thank you for doing this. It is so rare not to just leave users high and dry after a set time period. Huge kudos to Facebook for providing this for Parse users.
  • dimgl 11y ago
    Wow, that is a fantastic move. Much appreciated.
  • mentos 11y ago
    Awesome, I think a small tutorial on how to migrate an existing app from Parse to DigitalOcean would go a long way!
    • bogidon 11y ago
      Check this out: https://parse.com/docs/server/guide#migrating https://parse.com/docs/server/guide#migrating
  • deleted 11y ago
    [deleted]
  • microcolonel 11y ago
    Alternate title: “Facebook is opening Parse”
    • jfoster 11y ago
      It's actually incredible that they didn't position it that way.
    • crudbug 11y ago
      This would have changed the dynamics a whole lot. Opening up everything and running an instance on parse.com
      • crudbug 11y ago
        Just to complete this thought. Donating the project to Apache would have been great. I would have loved the Cassandra + Parse API integration.
  • intellegacy 11y ago
    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
    • gfosco 11y ago
      Migration is based on data size, but setting up the API server on a new VPS is quick... I'd say less than one hour from a fresh image on Digital Ocean. I'll try to publish a guide for that part.
      • intellegacy 11y ago
        that'd be great! thanks. please post the guide to HN or on the parse blog
      • ViccAlexander 11y ago
        This would be super awesome!
      • codek 11y ago
        Yes, that would be awesome! Please post a guide to move to digital ocean... Thanks and best; C
    • arungupta 11y ago
      You can also look at Couchbase Mobile that provides full power of a Couchbase database locally on the device. You can create, update, delete, query, sync and much, much more.
      • allsystemsgo 11y ago
        Easy on the spam buddy.
    • jamesjyu 11y ago
      Take a look at the full migration guide here: https://parse.com/docs/server/guide#migrating https://parse.com/docs/server/guide#migrating It'll really depend on your app, and how many features you used at Parse. In most cases, it should be easier than rewriting your entire app with Firebase, but you should carefully look through the guide and make that decision yourself.
  • crudbug 11y ago
    Are you releasing the admin dashboard code as well ? It will be easy to manage the server.
    • j45 11y ago
      This would be tremendous.
  • j45 11y ago
    Thank you for releasing tooling to deal with migrating as well as releasing the server itself. Too often services don't think about the full exit / shut down strategy and as disappointing as it is to see Parse go, it's nice to see it will actually live on in a way that can't be shut down by a corporate decision.
  • supster 11y ago
    Would it be possible to open source the Parse Dashboard? Even if it's just the data browser? I really loved that part of Parse.
    • techaddict009 11y ago
      They have already did that: http://blog.parse.com/announcements/introducing-parse-server-and-the-database-migration-tool/ http://blog.parse.com/announcements/introducing-parse-server...
      • rpedela 11y ago
        I don't see anything about the dashboard in the blog post?
        • techaddict009 11y ago
          Sorry my mistake. They have just open sourced the server not the dashboard. But some one has said they are going to open source the dashboard and all soon.
    • gfosco 11y ago
      We will work on that, yes.
      • supster 11y ago
        You guys are awesome. Thank you.
      • crtlib 11y ago
        That's great. I'm not regretting we chose Parse!
  • mtchll 11y ago
    thank you!
  • vixentael 11y ago
    would like to see some tutorial how to move parsedb&server to digitalocean or heroku
  • jchrisa 11y ago
    Kudos to Parse for providing an open source path forward. I know a lot of enterprise users who will only look at fully open source stacks, for a variety of reasons. It's good they are giving users a year to migrate. I expect Couchbase Mobile to see a lot of evaluations as this process plays out. I will be watching to see how the community grows. It looks like the ExportAdapter.js module in parse-server is low hanging fruit to connect to stuff like Couchbase Sync Gateway, which would give access to a multi-vendor ecosystem including IBM and Apache.
    • tleyden5iwx 11y ago
      [Full disclosure: I'm a FT Couchbase mobile developer] Agree 100% -- Parse deserves huge kudos for that move. Ex-Parse customers should definitely check out Couchbase Mobile, which has some functionality overlap with Parse and is already open source with several repos on github: https://github.com/couchbase/sync_gateway https://github.com/couchbase/sync_gateway https://github.com/couchbase/couchbase-lite-ios https://github.com/couchbase/couchbase-lite-ios https://github.com/couchbase/couchbase-lite-android https://github.com/couchbase/couchbase-lite-android At least you won't have to worry about getting "Parsed".
      • deleted 11y ago
        [deleted]
  • bribri 11y ago
    Wow you guys are awesome!
  • aikah 11y ago
    Kudos for opensourcing ! but : https://news.ycombinator.com/item?id=9693743 https://news.ycombinator.com/item?id=9693743 I guess the time spent ( a year ? ) on the Go version didn't help feature wise. The product didn't evolve that much in the meantime. I hope you provide a solution for cloud code and webhooks , webhooks at least , since cloud code is just javascript. Please be sure to host the documentation somewhere, like github pages. Good luck for your next project. I'd love to read a "post-mortem" once the service is definitely closed.
    • HectorRamos 11y ago
      While this is not specifically GH Pages, the documentation has been hosted on GitHub for quite some time now: https://github.com/ParsePlatform/Docs https://github.com/ParsePlatform/Docs
  • i386 11y ago
    This is a really classy way to shutdown your service. Well done.
  • Startups411 11y ago
    What about push notifications and Parse Config? Social apps that triggered push notifications now loose that functionality when moving to Parse Server, right? Also what about security? One of the beautiful things about Parse was not having to worry about servers and the security of back-end because you knew Parse was on top of it.
    • pferde 11y ago
      Depends on your viewpoint: One of the beautiful things about having your own back-end is not having to worry whether or not some 3rd party team is not neglecting security of the back-end because you know you are on top of it.
      • Startups411 11y ago
        You sound like somebody who feels comfortable handling security, but for boostrapped and/or a self-funded or even small funded startups, that's extra money that goes to plug a major whole that didn't exist with Parse because they made user authentication, permissions, and security simple. I'm no security expert. So now instead of concentrating on growing the user base, gaining traction and making the best experience possible for our users, that means finding, interviewing, and hiring more people to handle back-end security which takes a lot of time out of improving the product. How time consuming on a hours per day would it be to stay on top of handling security on your own? How many engineers would it take and at what cost per engineer?
        • pferde 11y ago
          Of course. Both approaches have their pros and cons.
  • manishkungwani 11y ago
    @gfosco Thanks for everything. Is the open-sourcing of Push delivery, Analytics, and Config, planned for the near future?
  • davedx 11y ago
    It really sucks Parse is closing down, it was one of the best alternatives to Firebase, indeed better for straightforward REST use cases, and I really enjoyed using it. It's nice that you've released an open source migration path. I hope somebody else can fill the niche of a fully hosted API-as-a-service. Best wishes.
  • tuyguntn 11y ago
    Hacker culture of Facebook makes it really valuable company in terms of engineering. Dropbox and Google (Mailbox & Reader at least) should learn something from them. Incredible move and good luck in future endeavors!
    • eru 11y ago
      Alas, open sourcing Reader wouldn't have done much: the code's all tied heavily into Google internal infrastructure. (Full disclosure: my team pulled the plug on Reader.)
      • cbeach 11y ago
        Interesting the Reader developers chose their own infrastructure over "best of breed" Google AppEngine?
        • ash 11y ago
          Google Reader initial release: October 7, 2005 Google App Engine initial release: April 7, 2008 https://en.wikipedia.org/wiki/Google_Reader https://en.wikipedia.org/wiki/Google_Reader https://en.wikipedia.org/wiki/Google_App_Engine https://en.wikipedia.org/wiki/Google_App_Engine
      • irox859 11y ago
        Oh you're the villain! But yes I can see that as joining a Blogger page in the Members widget automatically subscribed you in Reader.
        • eru 11y ago
          Alas, I joined after the damage was done.
  • joeyspn 11y ago
    It's sad that you are shutting down but I think it's awesome that you are releasing the platform source. Who knows, this could be the birth of a great FOSS project. 2k Github starts in 15h and growing...
  • MattRogish 11y ago
    Hey everyone looking for a migration path out - we have a “DevOps-as-a-Service” model where we can migrate Parse folks to AWS (not DO unfortunately) with full infrastructure automation, immutable infrastructure, autoscaling, chatOps deployments, monitoring and alerting, etc. for a flat rate. We have a platform that we’ve built that makes this possible - think of it as a Django/Rails/etc. for AWS: https://www.reactiveops.com/devops-as-a-service/ https://www.reactiveops.com/devops-as-a-service/ Although we have a framework, it lives in your github and runs in your AWS - there's no lock-in whatsoever. Ping me at matt [at] reactiveops dot com if you're interested!
    • lebnox 11y ago
      here, check out this link: http://www.shephertz.com/parse-migration-app42.php http://www.shephertz.com/parse-migration-app42.php
    • spimmy 11y ago
      Nice. These guys are legit. (RIP, Parse :( )
  • obelisk_ 11y ago
    I tried to use node on a $5 DigitalOcean dropplet a couple of times but whenever I tried to run npm to install something, it would run out of memory and be killed. Frustrated with this experience, I have stayed away from Node.
  • alyssoncm 11y ago
    I'm a web and mobile developer. Parse it is a good solution for a quick app backend setup but I never realized build big things over there. To me the most important to me is no vendor lock-in I see as very important to have full control over what I'm developing. I started to use a great platform http://parse.back4apps.com http://parse.back4apps.com and Im happy with the results. I recommend it as a migration option. At any moment you can have your code totally portable.
• ape4 11y ago
  Maybe its not such a good idea after all to code your app to a proprietary API in the cloud.
  • duncan_bayne 11y ago
    ... or a walled garden like iOS. But of course people will keep doing it, and keep complaining when the inevitable happens. https://xkcd.com/743/ https://xkcd.com/743/
    • sosborn 11y ago
      The walled garden has nothing to do with this.
      • duncan_bayne 11y ago
        ... which is why I used the word 'or'.
  • sktrdie 11y ago
    There is no such thing as "proprietary API". There are proprietary implementations...
    • dragonwriter 11y ago
      > There is no such thing as "proprietary API". I see you are unfamiliar with Oracle v. Google.
    • deleted 11y ago
      [deleted]
  • peterhadlaw 11y ago
    They were kind enough to release a compatible server for users to migrate to their own infrastructure to.
  • zenojevski 11y ago
• Mizza 11y ago
  Goddammit! I built a service on top of Parse and Yahoo Pipes. And I JUST finished porting the Pipe stuff to Lambda.. Oh well, nice of them to provide a DB migration tool and an open source server.
  • brianwawok 11y ago
    Upsides and downsides to roll your own. Your timing seems pretty unlucky though ;)
  • katowulf 11y ago
    Hang in there, you've got a year to figure out what's next. They're slipping out the door with good style at least.
• deleted 11y ago
  [deleted]
• sehr 11y ago
  Any specific reasons why? Always thought they were doing well, reasonably popular etc
  • steffan 11y ago
    Providing developer services is not Facebook's core business.
    • u320 11y ago
      So, you're saying we should prepare for the "Oculus shuts down" announcement?
      • steffan 11y ago
        If you see my other comment regarding this, that's exactly what I'm saying. It may never happen—I think Oculus may be closer to their core business—but if you're building on someone else's platform, you should be prepared for the possibility that the platform could disappear should it no longer be a part of that company's strategy. If you're building on Oculus as a platform, I applaud you, and I wish you and your product a long, healthy life. But have a Plan B. If it's not strategy, it's charity. And most corporations are not much given to that.
    • smt88 11y ago
      I don't think that's reason enough. AWS wasn't/isn't Amazon's core business, either. For a company that wants to be deeply integrated in all web-connected software, it makes sense to make it as easy as possible for developers to work with them.
    • gusmd 11y ago
      Why buy it, then?
      • profmonocle 11y ago
        I'm wondering that too. If it was just for the talent or a certain technology they probably wouldn't have waited so long to shut it down.
• mxstbr 11y ago
  That's a shame, I thought Parse was a nifty service!
• jamesfzhang 11y ago
  I am shocked...time for Fabric to build a backend?
• smt88 11y ago
  Does anyone know why this is happening? It was kinda buggy because of its Mongo foundation, but the concept itself was pretty great.
  • xyzzy4 11y ago
    Maybe Zuckerberg isn't passionate enough about it? Like buying a stock and then 2 years later you don't want it anymore, so you get rid of it.
• josh2600 11y ago
  It's really hard to build trust when products disappear. Building on top of google is hard for this reason, and Facebook is beginning to look eerily similar. Recall all of the wonderful social graph access that once existed and see, now, the wake of crippled API's where they once lived. Since it is impossible to build everything from scratch, some compromise must be made, but I wonder whether that compromise can reasonably include offerings from $BIG_CO? Certainly open-source projects implode as well, but rarely with the scale of things like Google Reader or Parse...
  • mikegioia 11y ago
    What's even more ridiculous is that their homepage says: From startups to the Fortune 500, hundreds of thousands of developers *trust us*. Trust you to what? Pull the rug out at some point? Why they even put that word on the HP is a separate question.
    • steffan 11y ago
      The acquisition happened nearly 3 years ago. To their credit, they kept running it for longer than a lot of other companies would have. Anyone in the situation of seeing their platform provider acquired should see the writing on the wall. It's unfortunate, but it's the reality. Enjoy the continued services while [if] they last, but always have a Plan B.
      • k-mcgrady 11y ago
        >> "Anyone in the situation of seeing their platform provider acquired should see the writing on the wall." In this case though FB seemed to embrace Parse and continued to develop it. It would have been much better to shut it down after acquisition. FB's support of it probably helped it gain more trust that it would stick around.
    • cballard 11y ago
      The extension of that sentence, when related to Facebook, is "dumb f*cks". https://en.wikiquote.org/wiki/Mark_Zuckerberg https://en.wikiquote.org/wiki/Mark_Zuckerberg
• TamDenholm 11y ago
  I just started developing something in parse in the last 2 months, i really really liked the platform, this totally sucks. Does anyone have any recommendations for alternatives with similar features?
  • philjohn 11y ago
    Running their open source parse platform server on your own infra?
  • codegefluester 11y ago
    They open sourced an API server that is fully compatible that you could host yourself http://blog.parse.com/announcements/introducing-parse-server-and-the-database-migration-tool/ http://blog.parse.com/announcements/introducing-parse-server...
  • nawazdhandala 11y ago
    Did you check out CloudBoost.io?
• khamoud 11y ago
  Well good thing this came out just now. I was literally about to start another parse project tonight.
• jewel 11y ago
  I am happy to see that they're not using any of the insulting language that would land them on http://ourincrediblejourney.tumblr.com/ http://ourincrediblejourney.tumblr.com/. FYI, here's the announcement of the acquisition from April 25, 2013: http://blog.parse.com/announcements/the-future-of-parse/ http://blog.parse.com/announcements/the-future-of-parse/ Relevant bits: Q: Will my Parse app be affected in any way? No. Q: Will Parse apps have to use Facebook functionality? No. Q: Will Parse honor my contract? Yes, of course.
  • golergka 11y ago
    This tumblr is so beautiful and so painful at the same time.
    • Animats 11y ago
      That's so great. The lifespan of "cloud" services is not long. It seems to be less than five years.
    • jmiserez 11y ago
      The post itself is an image right? With dark text on dark background? Why!?!
  • pbreit 11y ago
    So that will have been nearly 4 years ago.
    • tbranyen 11y ago
      Obviously you're not a golfer.
      • xyzzy4 11y ago
        Mark it zero!
      • deleted 11y ago
        [deleted]
• chasing 11y ago
  Which alternatives would people recommend?
  • humanfromearth 11y ago
    I would recommend Kinto. It's open source and used in production for mozilla browser sync service. https://github.com/Kinto/kinto https://github.com/Kinto/kinto
    • lebnox 11y ago
      Here, check out this: http://www.shephertz.com/parse-migration-app42.php http://www.shephertz.com/parse-migration-app42.php
  • delbel 11y ago
    firebase, it is owned by google. Or roll your own observer pattern pub sub document api service.
  • marknutter 11y ago
    I would recommend Parse. It's open source and used in production by thousands of companies. https://github.com/ParsePlatform/parse-server https://github.com/ParsePlatform/parse-server
    • xyzzy4 11y ago
      Looks like they don't support push notifications.
    • deleted 11y ago
      [deleted]
  • tbrock 11y ago
    Honestly, there are none, huge opportunity here.
    • gevaperry 11y ago
• adriancooney 11y ago
  Wonder why they actually shut down? Seems like it was an unexpected decision. http://blog.parse.com/events/announcing-f8-2016/ http://blog.parse.com/events/announcing-f8-2016/
  • mikegioia 11y ago
    It could be that they were giving away (for free) 30 requests/second and 1 million device installs.
    • abiox 11y ago
      that seems orthogonal.
  • lacker 11y ago
    The NYT article has some pretty good explanation here. http://bits.blogs.nytimes.com/2016/01/28/facebook-to-shut-down-parse-its-platform-for-mobile-developers/ http://bits.blogs.nytimes.com/2016/01/28/facebook-to-shut-do... "Facebook also would have had to invest untold millions of dollars in capital and, more importantly, engineering talent, to get the Parse business fully off the ground to have a better chance at making a dent in competitors like Amazon, Microsoft and Google." That old blog post doesn't make sense any more - we should just take it down.
    • wesleyfsmith 11y ago
      Must have been really hard shutting down your baby. Do you wonder what could have happened if you hadn't sold?
      • lacker 11y ago
        I do wonder, but it's just impossible to know. Working on a startup, there are just so many variables out of your control or understanding. You can't predict what will happen. You can only aim at a vision and do your best to get there.
  • 11y ago
• chrisfosterelli 11y ago
  While I'm sure this sucks for a lot of people, I'll be honest the shutdown seems pretty fair. One year notice, detailed migration path with accompanying migration tools, and an open source release of the product itself. I didn't use parse, but this seems like a reasonable way to do it.
  • ineedtosleep 11y ago
    Oh definitely. This is a fine example of how to do a service shutdown. Sadly, I await the comments from unprepared customers next year. If you make apps and use any sort of {P,B,S,I,}aaS, do you yourself a favor and follow/subscribe/whatever to their news/release channels.
    • mooreds 11y ago
      Yes! I wrote about this a few years ago: http://geekestateblog.com/monitoring-microvendors/ http://geekestateblog.com/monitoring-microvendors/ It's really important as people build apps (and business value) through composition of smaller services rather than composition of code that they become aware of these external dependencies. And not just at build time, but during the operation of these apps/business processes.
    • heraclez 11y ago
      I just received an email informing me of the shutdown
  • zem 11y ago
    also major props for being up-front about the fact that they're shutting down the service and they realise it sucks for their users, rather than some "incredibly journey" style bs.
    • mooreds 11y ago
      From the original post: > We have a difficult announcement to make. Yes, you can see their sheepishiness in the announcement. I'm sure it was a tough decision.
• minimaxir 11y ago
  Odd. The Parse SDK had a new release one month ago: http://techcrunch.com/2015/12/14/parse-launches-sdk-support-for-apples-watchos-2-and-tvos/ http://techcrunch.com/2015/12/14/parse-launches-sdk-support-... That makes this decision seem very sudden.
  • heraclez 11y ago
    And that's not all. Parse just did a full rebranding, including a full frontend overhaul of its dashboard. What the hell is going on?
    • timdorr 11y ago
      It's a BA came through and said "Oh, they're not making a billion dollars for us yet? Let's get rid of them!"
      • dalacv 11y ago
        BA?
        • pyb 11y ago
          Business Analyst
        • DonHopkins 11y ago
          Butthead Astronomer. https://en.wikipedia.org/wiki/Apple_Inc._litigation#Libel_dispute_with_Carl_Sagan https://en.wikipedia.org/wiki/Apple_Inc._litigation#Libel_di...
    • adventured 11y ago
      Deals often are on and then off or otherwise not necessarily expected to happen. In the midst of that, services typically and properly tend to push forward with what they were already doing as though no deal is going to happen. The worst thing you can do, is halt your progress during a negotiation.
• btown 11y ago
  It will be funny to see all of the abandoned apps that start failing a year from now. Obscure games, utilities, etc. Most people won't be bothered to go through the stress of an App Store review process to update an old free-to-play app that's not even making them revenue. But how many people's morning commutes will be ruined when their old games or news apps fall apart? The price of progress (and of liquidity), I suppose...
  • coldtea 11y ago
    >But how many people's morning commutes will be ruined when their old games or news apps fall apart? The price of progress The "price of progress" is suddenly not being able to play WhackAMole 3000 on your mobile phone on your way to work?
    • kennywinker 11y ago
      Kinda. I mean, I can dust off my old console and play the games on that any time I want. App Store stuff means built in expiration date. Cloud integration means built in expiration date. Price of progress.
      • ckrailo 11y ago
        Your old console ran the same code for years on end with no updates and no new features. Your phone's updating all the time. Thus, software TTL is much lower. (Software TTL for your console is determined by how long your cartridge serves up good data.)
  • oniMaker 11y ago
    Sometimes I like to think about how future archaeologists will be writing grand dissertations on the digital detritus we're all leaving behind today.
    • xyzzy4 11y ago
      And all the people who will try to revive 100 old abandoned source projects.
• browseatwork 11y ago
  Too bad. I admire them for giving people a year and giving some helpful tools. I'm glad Parse's winding down is less painful than "We're gone in 1 month, good luck, bye!". Another data point for the "Is PaaS dead?" conversation. http://blog.fortrabbit.com/cloudscapes-rerevisited http://blog.fortrabbit.com/cloudscapes-rerevisited
• grandalf 11y ago
  Wow. The 30 minutes you saved by using parse turns into a major headache. This makes me hesitant to use react and react-native.
  • rcchen 11y ago
    Why? React and React Native are both pretty core to Facebook's main applications these days (all of Instagram is written in React, there's a smattering of components all over the main Facebook page, and multiple Facebook-written applications are written in React Native, including parts of the main Facebook app). In contrast, Parse was more of a dev-infrastructure product that didn't end up impacting developer relations as much as Facebook wanted it to (I'm guessing)
    • grandalf 11y ago
      I love react and react-native ... this kind of announcement is scary though because Facebook is a big part of the ecosystem.
  • smt88 11y ago
    I'd be hesitant to use anything released by a large company that they don't use themselves for their flagship product(s). Angular 1 comes to mind. I believe Facebook does use React for facebook.com, but not React Native for anything in production yet.
    • nutate 11y ago
      React Native powers Groups and their ad manager: https://facebook.github.io/react-native/showcase.html https://facebook.github.io/react-native/showcase.html
    • sotojuan 11y ago
      Facebook uses RN for new apps—they're not going to rewrite their older apps because that takes too long and they work fine. They're also putting a lot of resources on it and hiring some smart people (Dan Abramov).
  • 11y ago
• Cshelton 11y ago
  It always sucks when things have to come to an end, however, this is a pretty graceful shutdown if you ask me. Many other service providers, especially in other industries, would often times send you a letter with a month, sometimes less, notice. From a business learning experience, I'm really interested in the reasoning. I'm hoping a detailed blog post comes out of this, which I'm sure it will, just as a "case study" of sorts.
  • hkmurakami 11y ago
    I feel like it reflects FB's character as an open source company.
  • HappyTypist 11y ago
    They have 1 year contracts with businesses. If they don't they'd get sued.
• subpixel 11y ago
  I'm building on top of Firebase at the moment, and this is exactly the sort of thing I'm afraid of.
  • teebot 11y ago
    I'm afraid google will kill firebase too. I built some sort of mvp with firebase and I intend to port it to express/postgres.
    • arungupta 11y ago
      Consider moving to Couchbase Mobile (http://developer.couchbase.com/mobile http://developer.couchbase.com/mobile). Why? - 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.
      • jaxondu 11y ago
        Too many spam posts from you about Couchbase Mobile. Anyway I do not see the similarity. Parse is hosted platform, build for mobile developers that do not want to self-host the backends, with affordable entry cost. Couchbase Mobile is a product offering with licensing and paid subscriptions for support, pricing has to be requested in order to know the exact, and the backends (Couchbase Sync Gateway and Couchbase Server) starts few thousands dollars per node. And we have to deploy and host the backends (whether we choose to buy or use the free community version). One can choose IBM Cloudant to host, but then Cloudant is hosting CouchDB compatible database and you'd miss the Couchbase Sync Gateway component, which is the main selling points (sync, offline) of Couchbase Mobile. Correct me if wrong.
• dantiberian 11y ago
  I wonder if Firebase will be next? They were acquired by Google in 2014. However they also acquired Divshot to join the Firebase team in 2015 which indicates they at least intended to continue with it then. Firebase does at least make more sense as part of Google's cloud services division rather than at Facebook.
  • mmanfrin 11y ago
    I think Firebase's position is a bit more defensible -- Google has done well to ingratiate Firebase as a backend for angular apps.
    • ravenkat 11y ago
      The news i have heard from various googlers is, `GOOG acquired Firebase because a project started using Firebase as backend and grew very fast and they didn't want to migrate and just acquired FireBase`.
      • boulos 11y ago
        This is not even remotely true. Disclaimer: I work on Google Cloud but not Firebase.
      • katowulf 11y ago
        Sigh. There should be a Snopes for Hacker News.
• gdeglin 11y ago
  One group of developers this is going to affect most are those who used Parse's GCM Server Key for push notifications. Since Parse is probably not going to reveal this key, Android developers using Parse for push will not be able to use their existing GCM push tokens with other services.
  • dozy 11y ago
    Parse authenticates with GCM using the API key that you provide, as do all other services AFAIK. So, all developers need to do is use that same key in their new push provider, and their push tokens will work. The tricky part is actually making sure that all of your push tokens that are in the Parse database are migrated to the push provider that you've chosen. EDIT: I stand corrected, looks like you have the option to use their key as you said, my apologies! Should have figured the founder of OneSignal would know ;-)
  • simscitizen 11y ago
    The easiest way to deal with this is to add your sender ID to the app manifest, so Parse registers with both its sender ID and yours: https://parse.com/docs/android/guide#push-notifications-setting-up-push https://parse.com/docs/android/guide#push-notifications-sett... This requires a new release of your app, but that is a necessity in any case.
    • gdeglin 11y ago
      You're right, it seems like this should work.
  • rpgmaker 11y ago
    And here I was thinking that because Parse was acquired by facebook using their Push notifications offering was as safe bet as I could make. Can anyone recommend an alternative short of implementing my own GCM server app?
• hkmurakami 11y ago
  >We’re proud that we’ve been able to help so many of you build great mobile apps, but we need to focus our resources elsewhere. I read this as "our Facebook overlords have decided that our revenue/head can be dramatically increased if redeployed on a different part of the overall company, so they have decided to shut Parse down and move us elsewhere." Which is a perfectly fair business decision but this is really sad to see since I saw the Parse acquisition as a beacon for platform companies being able to run independently post acquisition. :(
  • rms_returns 11y ago
    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.
    • joering2 11y ago
      you kidding?? Knowing what 200MM people are talking about and being able to display them "relevant" ads based upon it is priceless!!
      • estefan 11y ago
        The day I see ads on whatsapp is the day I leave.
        • joering2 11y ago
          Facebook owns whatsapp. You already making FB money even if you not crossing FB site. Actually you're working for Facebook... and you do it for free!
          • estefan 11y ago
            That's fine. I just don't want to be distracted by ads.
• DocSavage 11y ago
  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 http://kinto.readthedocs.org/en/latest/overview.html There's a nice table there comparing the different services' features.
  • chrstphrhrt 11y ago
    Whoah Kinto looks cool. Thanks for pointing that out. I'm one of the Ramses devs http://ramses.tech http://ramses.tech and we've been working on related problems from an "executable spec" angle. Seems backend automation is about abstracting storage/syncing and also about making development fast and accessible to different skill levels.
  • nawazdhandala 11y ago
    Did you check out CloudBoost.io? Its an open platform on Docker + also available as a managed service.
    • knicholes 11y ago
      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.
      • livingparadox 11y ago
        Thanks for the explanation in the edit. I also upvoted the comment for balance.
  • mayop100 11y ago
    [Firebase founder here] We're not going anywhere. We have strong backing here at Google and are continuing to make big investments in our platform. You'll see big things from us soon. What makes us different? Firebase is very complementary to Google's other product offerings. Cloud for one, as well as Angular, Polymer, GCM, etc.
• techman9 11y ago
  My thoughts: http://i.imgur.com/TnQRX6v.gifv http://i.imgur.com/TnQRX6v.gifv
• neemsky123 11y ago
  will you also open source the front end tools? i really loved the data explorers
• eachro 11y ago
  I used Parse a few years ago to serve as a backend for a simple event aggregation app. It was incredibly simple to use and integrate with. I probably spent on the order of ~1hr reading documentation and another 2 hours doing some quick and dirty implementation before having a functioning Android app. It's too bad it's shutting down, but I can't say I didn't see this coming after the Facebook aquisition.
• kuzmin 11y ago
  Currently using Parse for Push notifications (it's simple to send a request to Parse and it handles iOS vs Android issues). Is there any tool out there that has similar functionality? Ie. you register all your users devices there and they simplify the sending of push notifications.
  • dozy 11y ago
    Appboy, Kahuna, or (shameless plug) mParticle if you want multiple options :)
    • zippergz 11y ago
      Urban Airship too.
    • __abc 11y ago
      Urban airship as well I believe. I just remember typically finding Parse the easiest each time I had the opportunity to re-evaluate.
      • dozy 11y ago
        Yep definitely, Urban is a great option.
  • aglazer 11y ago
    It may be worth checking out Taplytics. We do transactional, behavioral and event-driven pushes (plus, you can A/B test all of it in one place) :) Disclamer - I work at Taplytics!
  • tomwilson 11y ago
    It's not quite as simple to use but Amazon SNS works decently and I doubt it will shut down any time soon :-)
  • gcarre 11y ago
    I just created an account on OneSignal: https://onesignal.com/ https://onesignal.com/
• yueq 11y ago
  This is much worse than Google closing Google Reader.
  • xyzzy4 11y ago
    Not as bad as when Google shut down Meebo though.
• shade23 11y ago
  Parse was the go-to platform for those who wanted to concentrate on their end product.I know people with (day to week)-old ideas who could set up the complete application using parse.It not only made life simpler for everyone but greatly supported rapid prototyping and not having to go through the hassle that comes with building your own stack.Yes I know there are combinations of several SAAS and IAAS which can fill the void,but no one can come close to the single stop solution that Parse provided. I hoped that Facebook would do with parse what Twitter did with Fabric(Yes I know that Fabric has ads as a business,but crashlytics is a god send for mobile developers). Nevertheless I hope more Parse like solutions are yet come.
• mmastrac 11y ago
  Ugh. This is why you don't build on proprietary stacks like this. I've detailed tonnes of complaints I've had about the platform itself being awkward and buggy in previous HN comments, but this is obviously the #1 reason not to. If Facebook can shut down a service this big, Google or Amazon can too. Moving a VM is (reasonably) easy, but porting an app from proprietary backend X to another is hard.
  • st3v3r 11y ago
    No, this is just why you should architect your applications so that the backend isn't all over the app, but instead limited to the outskirts. Then you can change providers at will.
  • akshaybajaj 11y ago
    I disagree that Amazon can shut down AWS at this point, half of the company internally runs on it.
• tmsh 11y ago
  Interestingly, might've been better to: a) release open source versions and announce pricing increase in the future. b) reduce people using the free 30 transactions / second limit. c) maintain in maintenance mode indefinitely. I just don't get why companies shut down services unless they're folding them into open source projects (like Freebase into Wikidata). Maintenance mode seems cheap to me, but maybe I'm missing something? I am most curious about Facebook's strategy for this. Total guesses - but maybe they have another developer platform in the works? Maybe it's just the focus on core businesses, but it is most curious. Anyway, I love parse! Cool it's open source now.
  • RussianCow 11y ago
    Keep in mind that this is Facebook, so it's likely they just had better things for those developers to do that would generate the company more revenue. It's not in Facebook's interest to keep a business running that's barely breaking even, especially when they can take the team and put it to use elsewhere within the company. (Not that I know what Parse's financials look like, but I'm guessing they aren't making boatloads of money.)
• carsongross 11y ago
  This is in no way to dog on Parse, which is handling the situation as well as any company I've seen, but I can't help but think of the hilarious line from https://medium.com/@wob/the-sad-state-of-web-development-1603a861d29f#.5barg65m https://medium.com/@wob/the-sad-state-of-web-development-160...: "A [Single Page App] will lock you into a framework that has the shelf life of a hamster dump" Seems like that could be said about a lot of infrastructure services out there as well.
• jtchang 11y ago
  One of the reasons you need to pick hosted services very carefully is just this type of scenario. Especially when you are deciding where your data lives. I give a tremendous amount of respect though to the Parse team for open sourcing the server. Like holy crap they released their entire code base. It must have been especially tough since you have to go through it and clean everything up. Too bad they didn't include the commit history (I certainly understand why they did it). Commit histories are generally the most interesting.
• fierycatnet 11y ago
  Hm. I personally haven't used Parse and I didn't even know they were with Facebook but I've seen it mentioned as a pretty popular back-end platform for Android apps (for example). What's the alternative then? AWS probably then?
  • nawazdhandala 11y ago
    I would not tie myself to a Cloud Platform but use open source stuff like docker which can be moved between Clouds. Btw, There's CloudBoost.io which is an alternative to Parse and is both on Docker (self-hosted) or as a managed solution at CloudBoost.io
    • boulos 11y ago
      Would you mind adding a "Disclaimer: I'm the co-founder of CloudBoost.io"? I've got nothing against you promoting your project when people need alternatives, but it's important that people realize you've got a stake in it. Like so: Disclaimer: I work on Compute Engine, but not Firebase ;).
      • estefan 11y ago
        I was reading an article just the other day saying how the web has made people feel the need to self censor, "apologise in advance", add disclaimers to everything they write, etc. because they're afraid to offend anyone these days since some people online are nuts. Unfortunately I can't find the link now... Disclaimer: I don't like disclaimers. Just write what you believe; unapologetically be you.
• PanosJee 11y ago
  And this proves that there no money to be made in Mobile developer tools. Pretty much all major tools have been acquired or face an uncertain future.
• mmanfrin 11y ago
  Man, this is an example of how to shutter a service gracefully. 1 year heads up and an open source replacement for their service with export tools to port the data in to a format that replacement can use.
• rajacombinator 11y ago
  Interesting. I guess I bought into the PR/propaganda that said Parse was a huge success and good acquisition for facebook. Never made sense to me why one would use such a service anyway.
• deleted 11y ago
  [deleted]
• free2rhyme214 11y ago
  NOooOOOoooOOOoooOOOooOOooo
• Kinnard 11y ago
  Why is parse shutting down?
• Danielmy 11y ago
  Hey guys, you can try www.backand.com which gives you anything that parse had to offer and much more. Real time, hosting, DB and server side action is just a bit of what they give you. Oh and the best part, it's free.
  • dmitriz 11y ago
    Is there anything that can keep backand.com away from the fate of Stackmob (http://venturebeat.com/2014/02/12/paypal-closing-down-backend-service-stackmob-months-after-buying-it/ http://venturebeat.com/2014/02/12/paypal-closing-down-backen...) and now Parse?
    • Danielmy 11y ago
      Unlike Facebook, backand main business is being a Baas. It has a lot of developers and fully backed. In addition, Backand's unique feature is that you can get the database connection and the server side configuration any time you want!
      • dmitriz 11y ago
        The first thing I read here https://www.backand.com/about/ https://www.backand.com/about/ is > "Backand’s proprietary technology". This means, if Backand will be acquired and shut down, all my time spent on learning specifics of Backand infrastructure will be wasted? Are there any plans to open-source the platform? That would give some guarantee and peace of mind.
• boggzPit 11y ago
  Damn it Facebook. Why did I ever believe you could handle being cool to developers?
• blasphemous 11y ago
  Kudos to Parse/Facebook for a somewhat graceful exit. However, i find it extremely foolish to shut this down completely from Facebook's point of view. Sure redeploy all the gun developers to other FB products, but you can't tell me FB could not afford to hire some devs to maintain this service. They could have sold the service to another company too. This just gives Facebook more bad vibes from the dev community.
• Raed667 11y ago
  I used Parse for a dozen projects, but none in production, and all were free. To be honest, I loved how Parse allowed me to focus on the App/product without having to worry about APIs and backend. However whenever I'm serious about an App I end-up investing in some PHP or Node .. This is probably true for a lot of people and this is why it is probably shutting down.
• purans 11y ago
  Looks like time to revive my PubKit - https://github.com/narup/PubKit https://github.com/narup/PubKit
• muzani 11y ago
  Well, this sucks. My company is about to get acquired for our technology. A huge part of the tech relies on Parse. I mean they were charging for it! Who would think that they will shutting down? I guess we'll have to rebuild that part from scratch starting right now.
  • ergothus 11y ago
    Not from scratch, since they are offering the server code on github (see top comment here)
    • bsaul 11y ago
      i would not be surprised to see a company reusing this code to provide a 100% compatible service in the coming month.
      • st3v3r 11y ago
        Just one?
• pbreit 11y ago
  You would think they could have found someone to take it over?
• chatmasta 11y ago
  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 the towel on what seemed like a good plan to gain a foothold in the cloud space. Either that, or they're not really shutting down, and they just want to get a bunch of free labor from open source developers before migrating to an enterprise support business model.
  • rizjoj 11y ago
    I always suspected that Facebook's purchasing of Parse was an aquihire. (I've used Parse from 2012-2013)
  • adrr 11y ago
    Isn't Instagram still using AWS for some of their infrastructure? They had a big blog post about moving but if i remember correctly there was article about instagram getting hacked via S3 bucket keys a couple months back.
  • wkoszek 11y ago
    You mean main FB data-centers? The reason can be as simple as security standards used in both services may not be compatible.
• droithomme 11y ago
  Platforms are for the naive. After a few turns at the merry go round the newbie developers learn this hard lesson.
• nawazdhandala 11y ago
  Open Sourcing the platform is always the good thing. Probably both Twitter Fabric and CloudBoost.io will be the next Parse out there. CloudBoost.io is open on Docker and is both self-hosted or managed.
  • doRadiology 11y ago
    Wanted to downvote for spamming the thread with endless cloudboost.io postings... clicked upvote instead. Oh well..
• eva1984 11y ago
  This is bad...Cannot imagine how many people will freak out when AWS shut down....Just kidding
• nodamage 11y ago
  This announcement just underscores the importance of having full control over your backend. Yes, it's more work, but if you're writing apps that seriously depend on backend services, it's simply too much risk to depend on anyone else. Fortunately in this case Facebook offered generous lead time to migrate off Parse.com, but they were not obligated to do so, and other providers might not be so generous in the future. Developers who depended on Parse now have an interesting decision to make: export their data into MongoDB and start running their own servers, or look for an alternative BaaS provider to do it for them (which carries the same risk of that provider shutting down in the future).
  • nawazdhandala 11y ago
    ... or use an open source BaaS which can be self hosted or managed like CloudBoost.io
    • nodamage 11y ago
      Yes, self-hosting falls under "owning your own backend". The managed option carries the same risk of shutdown as with any other provider. I think you can stop spamming your website in this thread now that you've mentioned it a half dozen times though.
  • intellegacy 11y ago
    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
    • asadlionpk 11y ago
      Firebase is good for small hackathon-like projects and it gets ugly when your DB grows. Not much optimizations you can do.
      • mayop100 11y ago
• elcct 11y ago
  I always thought of Parse as a service for someone too lazy to setup mongodb. But to be serious, I think that was a nice tool to get ideas up and running for testing purposes. Running in production? Hell no.
  • intellegacy 11y ago
    What would you recommend? Im' a new app developer. Debating whether I should begin using Firebase or .. what you just said. The thing is, there are articles guiding me through using Firebase. I'm not sure there are articles telling me how to setup mongodb and where
    • simpfai 11y ago
      I guess it depends on what your aims are. Are you new to mobile development in general and just want to learn how to develop for your preferred platform(iOS, Android etc..)? If thats the case then definitely use Firebase or any other backend as a service for that matter. This will allow you to focus on building your app and not have to worry about implementing an API that provides access to your mongodb database(this would also be a worthwhile exercise). Hope that helped.
• WoodenChair 11y ago
  Suddenly, Apple's CloudKit doesn't seem so unattractive - but at the same time I fear it will face a similar fate. Anyone have any insight about whether it's "safe" to build upon? Is there yet an Android solution for connecting to their REST API?
  • hamming 11y ago
    AFAIK, the new Photos app in iOS and OS X are built on CloudKit. So I assume it will only die when iOS dies, which could be another decade or so.
    • WoodenChair 11y ago
      Well, that's not much reassurance because they stopped publicly selling/supporting WebObjects long before they stopped using it themselves.
      • schwarrrtz 11y ago
        Pretty sure they still use WebObjects for iTunesConnect (at least).
  • giarc 11y ago
    Wow - the dashboard looks close to Parse's new dashboard. https://developer.apple.com/icloud/images/cloudkit-dashboard.png https://developer.apple.com/icloud/images/cloudkit-dashboard...
• jamessteininger 11y ago
  Why did this happen?
• crudbug 11y ago
  Just signed up for a new account .. new beta dashboard looks sleek. Are they open sourcing the ReactJS code ?
• mdevere 11y ago
  Er, what happened here? Parse was a great product.
• hasenj 11y ago
  It seems that no few months can pass without some "X as a service" gets shut down. I basically now have the following assumption by default every time I see a new startup: What ever they are doing now, it will probably be shutdown within the next 4 years (assuming it gets any success at all in the first place).
• dmitriz 11y ago
  So is the Firebase the next one?
• simple10 11y ago
  Anyone used CloudBoost.io and can recommend it as an alternative to Parse? https://cloudboost.io/ https://cloudboost.io/
• deleted 11y ago
  [deleted]
• brooklyndude 11y ago
  I can say one thing? Firebase. That's it. Just one word. :-)
• lsiunsuex 11y ago
  wow. A year ago when I rewrote my startup's product in AngularJS I was on the fence between Firebase and Parse. Built prototypes against both and ended up going with Firebase for a few reasons - 1: price, 2: owned by Google and not FB and 3: the whole 3 way data binding thing. Awesome to see them releasing code for the backend but I'm finding this trend really disturbing - relying on 3rd party services for everything. Doesn't anyone remember back in the day (like 5 years ago hah) when programmers / admins actually bought software and ran it on their own servers and didn't "rent" it? I know, crazy right? To own software and if the company went under, things could still be fine for a while longer. Maybe it's time to consider my use of Firebase and go back to the way things used to be.
  • mayop100 11y ago
    [Firebase founder here] I want to help put your mind at ease. Google is 100% behind us. If you have specific concerns, please ping me on Twitter: @startupandrew
• Yhippa 11y ago
  http://www.businessinsider.com/why-facebook-acquired-parse-for-app-acquisitions-2013-9 http://www.businessinsider.com/why-facebook-acquired-parse-f... > Apps currently hosted by Parse include Food Network, Hipmunk, iBart, Anypic, and Travel Channel. There are 100,000 apps using Parse, Graham says. Article is 3 years old but wonder if they've moved on from Parse?
• davidkhess 11y ago
  Seems telling that Facebook chose to shut it down rather than spin it back out on its own or sell it. That implies the economics of it weren't working.
• datarem 11y ago
  It's as if millions of independent developers cried out in terror and then suddenly migrated to DigitalOcean.
• boulos 11y ago
  To those concerned about Firebase, here's the latest tweet from Firebase: https://twitter.com/Firebase/status/692845862527995904 https://twitter.com/Firebase/status/692845862527995904 > Not a great day for app developers :( Firebase is healthy & actively working on many new exciting features here at Google #parse Disclaimer: I work on Compute Engine not Firebase (but I sit next to them).
• sciencesama 11y ago
  http://venturebeat.com/2015/08/28/parse-ceo-ilya-sukhar-is-leaving-facebook/ http://venturebeat.com/2015/08/28/parse-ceo-ilya-sukhar-is-l... when a venture capatilist leaves the team things are not going good somewhere ;)
• nevi-me 11y ago
  I haven't worked with Parse, but the announcement reminds me of something I decided to do as much as I can. We sometimes choose to build features on top of third-party vendors' services, and the reality's that unless that third-party derives decent revenue or primarily provides that service; one shouldn't expect that the service will always be available. Twitter was a good example, Google SEO is another, where people who were relying mostly on search traffic got wiped when algorithms were changed. It takes longer at times, and seems like reinventing the wheel, but for features that I deem to be very useful to my users, I choose to roll out the relevant underlying detail myself. In most cases there are often already third-party libraries that can help with bootstrapping the features. I'm glad that the parse-server is available so people can run their own local instance though.
• ryeguy_24 11y ago
  This is exactly why I chose to implement everything myself rather than use a cloud wrapper.
• spdustin 11y ago
  I hate to be "that guy", but I use their analytics too, along with in-app push notifications that can be targeted to groups of users. Anyone have experience and recommendations for alternatives that are just as easy to implement in an iOS or OS X app?
  • weitzj 11y ago
    Mixpanel
  • giarc 11y ago
    I'll second MixPanel, but also Fabric.io (their crashlytics product).
  • Startups411 11y ago
    I use Google Analytics, Flurry Analytics, Facebook Analytics and Fabric all with custom events. Fabric is great for real-time. Mixpanel seems to be extremely costly depending on what type of app or game you have. For broadcast push notifications, I use PushWoosh. They have a lot of features that Parse Push doesn't for broadcast notifications. As for the in-app client-based push notification triggered by liking or commenting on a post or profile, I have no idea how to replace that without Parse. Hopefully they'll included some sort of guide to help with that migration.
• bsaul 11y ago
  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, but simply because they're exactly in the same case (proprietary,non standard, critical technology, held by a company who don't really care about it for its money service). People won't sign up on firebase anymore, so they will have to shut down quite soon. 4/ Every non core project run by facebook should be looked upon with extra caution now. Yes, that includes occulus. They're clearly not going to sell many devices, and gaming console maker (aka Sony) will have the lion's share of the gaming market. So, expect fb to shut it down in 2 or 3 years if it doesn't get a very large marketshare (the only use case large enough i can think of that is not gaming being porn). 5/ I personnaly would be really hesitant now to run on something like google app engine. I wouldn't be surprised to see google and microsoft moving forward api standardization for core cloud services on a much faster pace. Except amazon, nobody is really safe now.
  • akent 11y ago
    Firebase disagrees with you https://twitter.com/Firebase/status/692845862527995904 https://twitter.com/Firebase/status/692845862527995904
    • vonklaus 11y ago
      I agree that Firbase is a ool option and probably safe as they recently took steps to lock it into the google account. Someone will inevitably say google kills projects often, but they probably won't kill this. Alphabet's strategy seems to be yo onboard new developers and get into mobile.Firebase is a good way to begin that pipeline allowing new devs into googles ecosystem and controlling how tags work on websites by creating their own library and pushing people in. Why did parse fail though? Seems like a good strategy for Facebook.
    • st3v3r 11y ago
      To be fair, would they say anything else? Even if Google had plans of shutting them down in 3 months, it's not like they'd come out and say, "Oh, we'll be joining parse next quarter."
• lucb1e 11y ago
  Either their mobile home page is broken or it only shows this announcement anymore, but what is Parse anyway?
  • babuskov 11y ago
    I wondered the same. Wikipedia page sums it up: https://en.wikipedia.org/wiki/Parse_%28company%29 https://en.wikipedia.org/wiki/Parse_%28company%29 "...back-end tools for mobile developers that help mobile developers store data in the cloud, manage identity log-ins, handle push notifications and run custom code in the cloud." AFAICT, it was doing all the mundane work you need to get a modern mobile app up and running. So, developers could concentrate on the business logic of their application and leave the rest to Parse.
  • 8note 11y ago
    > what is _____ anyway? I feel like that's a relevant question I have for most HN posts
• fnayr 11y ago
  If you're making (mobile) games and looking for a replacement, I cannot recommend Gamesparks[1] highly enough. Their documentation is way behind Parse's (which has excellent docs), but their features (relevant to games) and customer support are far superior, and they are actively working on improving their docs. [1] http://www.gamesparks.com/ http://www.gamesparks.com/
• chx 11y ago
  Charity Majors leaves Facebook/Parse, Parse shuts down. I am not surprised.
• Amituchens 11y ago
  This is going to be a pain
• 20years 11y ago
  I was just looking at Parse & Firebase for the potential back-end on a biz app I am currently developing. I decided to install DreamFactory on AWS with DynamoDB because I felt uneasy relying on the others. I have been burned multiple times by both Facebook & Google shutting down API's. It was fairly painless getting DreamFactory setup. I give props to Facebook for giving such a long notice though. That should be more than enough time for app developers to switch.
• Symbol 11y ago
  My sympathies to any workers displaced by these events, but I'm happy. Parse is a bad product: it has weird quirks in normal usage but most importantly scales abysmally. I'm thrilled to have ammunition to justify moving away from it. Love love love the open source angle however, and wish more sunsetting products go this route.
• markpiller 11y ago
  It is a sad day and I feel for the developers who got caught in the situation. If migrating to your own server is not an option, consider Backendless (https://backendless.com https://backendless.com). We are stable and healthy and we have a team to help you with the migration of your app.
• samuraicode 11y ago
  Parse was how I got my first backend needing apps into the App Store. Always thought they were a great company and really set the bar for how to build and document an API. Sad to see them go, but wish them all the best.
• sodafountan 11y ago
  Facebook's stock is up 15% today. If they're this quick to kill off products and services then long term I'm bearish on them. Zuckerberg just came back from paternity leave and he announced a one month vacation next month. I don't think his head's in the game. Get rich and stop trying I guess?
• bsdpython 11y ago
  There are going to be a lot of mobile "full stack developers" that are going to have to scramble now to find another way to avoid learning how to build a simple API server and database. I only used Parse for one small project a few years ago. At the time their scheduled tasks feature was new and I found it hilarious that there was a bug that mixed up hours and days in the scheduler. That is when the scheduled tasks actually ran at all.
  • jonsterling 11y ago
    Lol yep, it was horrible.
• deleted 11y ago
  [deleted]
• nomane 11y ago
  Noamane ell
• Everhusk 11y ago
  Dang. I literally just finished building my first app with React Native/Parse two days ago. Was really amazed by how easy the stack was to get production ready, but now? Heigh ho, heigh ho, its off to work I go... :(
• tawrahim 11y ago
  So what happens to the parse credits? Do we get the money back?
• theDevDude 11y ago
  So this is how companies, who offer cloud services, are trying to get us, the devs, to trust them... WELL PLAYED FACEBOOK!!!!!!!!
• deleted 11y ago
  [deleted]
• theDevDude 11y ago
  So, this is how Facebook wants the devs to trust them?!? Let alone trust other cloud services companies??? WELL PLAYED FACEBOOK!!!!!!!!
• pashakym 11y ago
  link to Parse customers VEVO, Volvo, Udacity, Eventbrite, Orbitz, Ebay, Groupon, Hipmunk, MTv, Playtika, EBATES, SAMSUNG and many many others https://webcache.googleusercontent.com/search?q=cache:ZL4JyMJyYYMJ:https://parse.com/customers+&cd=1&hl=en&ct=clnk&gl=us https://webcache.googleusercontent.com/search?q=cache:ZL4JyM...
• deleted 11y ago
  [deleted]
• noodlio 11y ago
  We are hosting a poll on Twitter asking which competitor will benefit the most from this. View the results and participate here: https://twitter.com/noodl_io/status/692856647555788801 https://twitter.com/noodl_io/status/692856647555788801
• arungupta 11y ago
  [Couchbase Developer Advocate] Consider moving to Couchbase Mobile (http://developer.couchbase.com/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.
• theDevDude 11y ago
  I will NEVER trust Facebook again to build products! In fact I will stop using their products and I urge you all to do the same!
  • pashakym 11y ago
    you better focus on something enterprise oriented.
• ali_oguzhan 11y ago
  OK. i ve read all comments here. literally. why no one mentioned baasbox? i am building a mobile app with parse and now considering to move it to the baasbox on my own server. And no one here mentioned them. something wrong with it? http://www.baasbox.com/ http://www.baasbox.com/
  • alyssoncm 11y ago
    Parse it is a good solution for a quick app backend setup but I never realized build big things over there. To me the most important to me is no vendor lock-in I see as very important to have full control over what I'm developing. I started to use a great platform www.back4apps.com and Im happy with the results. I recommend it as a migration option
• jondubois 11y ago
  Maybe it's a good time to self host an open source solution using http://socketcluster.io/ http://socketcluster.io/ maybe with the Meatier stack https://github.com/mattkrick/meatier https://github.com/mattkrick/meatier
• fomojola 11y ago
  Is there an opportunity for a 3rd-party hosted Parse service? Seems like that may be an option for the folks who are currently using Parse and need to move: someone to basically run the open source service on top of AWS/Linode/Digital Ocean/Google Cloud for a nominal fee.
  • pseudobry 11y ago
    https://cloud.google.com/nodejs/resources/frameworks/parse-server https://cloud.google.com/nodejs/resources/frameworks/parse-s...
• estraschnov 11y ago
  There are some other tools that let you build an app without backend code. Here is ours https://bubble.is/developers https://bubble.is/developers, would love to hear from folks.
• partisan 11y ago
  Can I have the domain name?
• gsklee 11y ago
  Seriously, any good alternatives other than Firebase? I chose Parse because it looks better than Firebase... this latest development is beyond me. Such a promising product...
• drchiu 11y ago
  Definitely kudos to Parse for open sourcing what is essentially their platform. Nonetheless, this speaks to the difficulty many of us in the startup world face when choosing our technology stacks. Parse, Firebase, and other similar BAAS platforms are very attractive for a variety of reasons. But in the end, many of them get acquired and eventually wind down, or run out of money because it's so difficult to run profitably. Selling to developers is oftentimes a difficult thing to do. I've seen multiple products aimed at developers that look great and get me excited, but when I sit down and really analyze it -- each of them have yet to make even a single dollar from me. I'm sure many of us are in similar positions.
• bogidon 11y ago
  Looks like the Parse dev team is going to continue development of the SDKs for now: https://github.com/ParsePlatform/ParseUI-iOS/issues/189#issuecomment-176529129 https://github.com/ParsePlatform/ParseUI-iOS/issues/189#issu...
• mpinteractiv 11y ago
  I love your product, thanks for releasing a "community server". I liked it because it contained enough business logic to get started with most projects. Built that with it among other things : https://github.com/Mparaiso/playground https://github.com/Mparaiso/playground ( a jsfiddle lite directly available on github , the UI is angularjs : https://mparaiso.github.io/playground https://mparaiso.github.io/playground ) So thanks. You were the best BaaS feature wise IMHO. EDIT: however just one point : you took 1 year to rewrite your API in Go, which yielded performances but the product didn't evolve that much in the meantime because of the rewrite, was the experience positive or negative?
• andrewbellay 11y ago
  If folks need help migrating, you can get it done quickly and cheaply with some help from Toptal (http://www.toptal.com/#select-uncanny-hackers-today http://www.toptal.com/#select-uncanny-hackers-today) -- this sort of stuff is right up their alley..
  • pc86 11y ago
    Don't spam please.
  • dang 11y ago
    We detached this subthread from https://news.ycombinator.com/item?id=10991745 https://news.ycombinator.com/item?id=10991745 and marked it off-topic.
• praveenweb 11y ago
  I would like to see a detailed explanation from Facebook on the business front for closing Parse. Developers would now be skeptical about using any Proprietary service for their backend.
  • lacker 11y ago
    I suggest reading http://bits.blogs.nytimes.com/2016/01/28/facebook-to-shut-down-parse-its-platform-for-mobile-developers/ http://bits.blogs.nytimes.com/2016/01/28/facebook-to-shut-do... . I think that is a really good article describing the situation.
• bikamonki 11y ago
  Many thanks for a great product, for giving away the server code and migration tool but...no thanks. The whole point is that many of us don't want to run the back-end. We cannot afford to do so, we are not fully qualified to do so, our clients will not pay us more to do so. Anyone else selling a similar service? I'm up for grabs!
• henrify 11y ago
  I don't understand their decision. Developers are crucial for Facebook's success as platform, and the amount of distrust and bad-will they just gained would seem to far outweigh their cost savings in grand scheme of things.
• 666_howitzer 11y ago
  I'm using parse push notification service, is it still working?
• tranv94 11y ago
  I came to enjoy Parse, but alas I have $600 in credits from it. Any ideas I should use it for?
• yamill 11y ago
  I think Parse is an awesome platform and was really well documented. I used it for building my app, and will probably end up migrating to my own parse server and then decide where to go from there. Parse really made it easy to get an app running. Especially a couple of years ago, when api's were complicated. I'm going to miss the push notifications, I just implemented them and they work really well. Hopefully an open source solution will get released so we can continue using them.
• vinceyuan 11y ago
  Facebook spent $85 million buying Parse in 2013. Now it will be closed. I used Parse. But I found it's expensive if you want to use some Pro features. I built my own server on a cheap VPS later.
• mjrthemes 11y ago
  Next thing Facebook will close will be React. Remember this comment.
• flanbiscuit 11y ago
  Damn, I just added Parse to a small project. Does anyone have a suggestion for a good service that handles Push notifications like Parse? I really don't want to set up my own server for this.
  • hkal 11y ago
    I'm in a similar situation. Currently looking at OneSignal (https://onesignal.com/ https://onesignal.com/). Definitely open to other suggestions if anyone has any.
• Spoom 11y ago
  Parse is a great provider for push notifications, having only really gone down once in the time we've used it (and also being, well, free). I didn't use any other part of the system because we had our own databases and whatnot, but it is great for push. It will be missed.
• giarc 11y ago
  What is Facebook retaining? There must be something they are holding onto. Would it make any sense for FB to give the original founders the option to buy back Parse? With them open sourcing most of the product, what could they still have?
• sb8244 11y ago
  One thing that I haven't noticed in the comments is that the released server is parse API compatible. It is not the parse server, and so you aren't guaranteed the same things you are guaranteed from the real parse service.
  • HectorRamos 11y ago
    The "real" Parse service is built to power hundreds of thousands of apps. The OSS Parse Server you run yourself would only need to power a single app. Two very different use cases.
    • sb8244 11y ago
      Yes, but it seems that everyone thinks that this is the "Parse Server" being released. It's not, it's just an open source compatible API. It's important because a lot of the powerful features of Parse aren't included in the new open source server (analytics, config, push). Saying that Parse is open-source seems to imply that these powerful features are available.
• vitalychernobyl 11y ago
  Very very disappointing. Parse was a great platform and Facebook killed it. I guess it's going to be full stack AWS all the time forever. They shouldn't have bought it if this wasn't going to be a core part of the business going forward. Boo, Facebook!!
• Nemant 11y ago
  Next thing you know is react/react native is no longer supported
  • intrasight 11y ago
    can only hope ;)
  • eyko 11y ago
    How's that even comparable. React was released as open source from the beginning.
• pavlov 11y ago
  My take on this turned out too long for a comment, so I wrote a blog post: "Facebook’s Parse shutdown has a lesson to all tech customers" https://medium.com/@pauli/facebook-s-parse-shutdown-has-a-lesson-to-all-tech-customers-ecc43a83e36b#.vo0vdf37f https://medium.com/@pauli/facebook-s-parse-shutdown-has-a-le...
• alexmk92 11y ago
  When the news first hit I was a little disappointed but after reading through the "what to do next" post I am extremely impressed by the way Facebook are handling this. A year to let us all migrate is more than generous, and an open source server will allow us all to continue to rapidly build our applications. I don't mind fiddling around with scaling a little through the AWS console.
• wkoszek 11y ago
  When I first learned about Parse, I started to wonder how giving away 20GBs with 30req/s generates money, and I think now I have an answer.
• weakwire 11y ago
  So you mean Facebook is open sourcing Parse...
• elkhourygeorges 11y ago
  Why did they do this? Parse was on track to disrupt the cloud. Why do you need a full backend when you can easily define APIs and access them through mobile and web?
• mikaelmorvan 11y ago
  If you want to move to an other BaaS, ZetaPush provides NoSQL as a service, File storage as a service, Search as a service and lot's of other things for mobile, web, server and IoT
• patkai 11y ago
  Kudos to the Parse team for many things, including a much more decent exit than many others. But aside all my admiration for all their achievements - all beyond my abilities - let me ask you, hackers of the world, is this what we really want, if/when we build something so awesome? I do prefer to hear DHH talk stuff like "Basecamp is my life's work".
• manishkungwani 11y ago
  My thoughts on the closure, and options moving forward. http://mk.bloomcs.com/parse-com-is-dead/ http://mk.bloomcs.com/parse-com-is-dead/
• orasis 11y ago
  WHAT THE FUCK!!?? Facebook just obliterated any shred of developer trust it once had.
• js4all 11y ago
  Coincidentally we recently added MongoDB to our range. So, if you don't want to do devops yourself, our fully managed stack may be an interesting migration path. First app is free. https://cloudno.de https://cloudno.de
• jaxondu 11y ago
  Speculations on why the shutdown: Apple CloudKit is gaining momentum. Google is predicted to come out its own offering for Android based on Firebase. Facebook wants focus on its Messenger as a platform, rather than 'supporting' Apple and Google's platforms. My 2 cents.
• scriptstar 11y ago
  Totally disappointed with this announcement. Facebook is making billions of dollars of profit but can't keep up the lights at Parse. I will think twice to jump on these platforms next time. Now, I am more sceptical of using ReactJS, ReactNative and other stuff from the FB spearheads. Perhaps a high time to learn typescript and angular2.
  • adamors 11y ago
    You should be skeptical of every third party service/platform by now.
  • codeisawesome 11y ago
    ReactJS is a no-no from the get go. Facebook's Patent grant on what is supposed to be an "open source product" is ridiculous: https://github.com/facebook/react/blob/master/PATENTS https://github.com/facebook/react/blob/master/PATENTS. "If you ever start a patent conflict with Facebook in court, (worse but even more likely:) or if Facebook starts a patent litigation against you, you LOSE all your rights to use React in ANY product throughout your company and MUST stop using it at once in your code!" Imagine how that can bring a team down. If folks know of anything out there that works like React (I like the ideas, including JSX) but isn't hobbled simply by mis-virtue of being "backed" by the characterless evil that is Facebook, kindly enlighten me, I will use it. I'm actually wondering if the new "open source" Parse code will have the same Patent horror built-in, and if yes that's even worse considering backends can be even more complicated and important part of a company's infra. Also, I'm sure there are people saying "hey, your work may not be significant enough to cause a Patent violation with Facebook so you and the majority of library users are safe". Sure, that is likely true. But it's about the principle.
    • codeisawesome 11y ago
      Here's an answer I found: Vidom (https://github.com/dfilatov/vidom https://github.com/dfilatov/vidom) It's faster than React or Angular 2 in one benchmark methodology: http://www.stefankrause.net/wp/?p=218 http://www.stefankrause.net/wp/?p=218
• markatkinson 11y ago
  I wonder if Firebase is doing somersaults...
• pajop 11y ago
  has anyone here tried http://www.kinvey.com/ http://www.kinvey.com/ ?
• krmboya 11y ago
  So, just some unanswered questions in my mind concerning startups that get bought out then shut down. Do they end up creating more value than was invested into them in the course of their lifetime? Who captures most of this value? What does this mean for technological innovation and increase in productivity in general?
• maxko 11y ago
  Suddenly! I just finished pretty complex app which relies on Parse, can anybody recommend some alternative service? I have looked at Kinvey, but it seems too expensive. Does anybody have experience with Backendless?
• exodust 11y ago
  The parse blog crashes my Firefox browser. Even in safe mode and without javascript the browser crashes. Also, trying to close my Parse account is impossible. Then I found this on their FAQ: "Currently, there is no way to delete an account. You can just stop using it; we won't spam you." But they did spam me, I got an email from "FocusVision an independent research firm via Facebook." asking me to take a survey about Parse. I have nothing to do with Facebook, never had a Facebook account, never will. I'd forgotten Parse was acquired by Facebook.. now I remember the "it won't change anything, we're not going anywhere" blog posts from 2 years ago.
• rhapsodyv 11y ago
  I'm trying to find the reason. Anyone can point me where I can find?
• DivineTraube 11y ago
  CEO from Baqend here. This announcement will have a huge impact for the mobile dev community that relies on Backend-as-a-Service systems. I personally think that Facebook had several reasons to shut down Parse: 1) The technology stack was really fragmented and often rewritten in large parts. I still have this statistic in mind how their 200 Rails API servers were only able to serve 15 requests/s each [1]. If you look at the database technology inside Facebook, there is much superior infrastructure that was never really integrated into Parse (Haystack@OSDI'10, Tao@ATC'13, F4@OSDI'14, Extended Apache Giraph@VLDB'15, RocksDB, etc.) 2) Parse did not have a core competitive advantage: it was just the first company to whole-heartedly pick up the BaaS-paradigm with sufficient man power and a good understanding of developers' needs. The technology itself was not particularly innovative in any way, just (mostly) solid engineering. However, there remained really basic limitations that were never addressed [2]. For instance the only (!) way to safely handle concurrency control was through counter data types. 3) The model of Parse promotes independent apps and websites outside the Facebook universe. 4) The pricing in increments of guaranteed 30 requests/s was okay for simple apps but absolutely useless for anything beyond that. In particular for websites which as of 2016 do an average of 100 requests per page load [2] a single user can leave a Parse app rate-limited or down. The main asset of Parse were their great client SDKs and well-written documentation. This is why we made a plan: we will fork the Parse SDKs to offer seamless continuation of apps relying on them, including Push and the other features dropped in the open-source Parse Server. We opted for this approach as the Parse Server implementation on Github looks really brittle and the convoluted Parse REST API is really not an option. By doing this we hope to provide a scalable and long-term solution for developers looking to continue their Parse-based apps. Baqend [2] is a pre-seed startup founded out of the database research group at the University of Hamburg (Germany). Our product launching into production within the next months uses a new approach to consistent web-caching reducing latency in common web workloads by up to an order of magnitude [5]. It is due to this background that we very eager to not only provide great usability (which Parse also did) but also acknowledge the need for complex data processing: low latency access, partial updates, continuous queries and ACID transactions. We'll post a detailed plan on our blog, soon. [1] http://blog.parse.com/learn/how-we-moved-our-api-from-ruby-to-go-and-saved-our-sanity/ http://blog.parse.com/learn/how-we-moved-our-api-from-ruby-t... [2] http://profi.co/all-the-limits-of-parse/ http://profi.co/all-the-limits-of-parse/ [3] http://httparchive.org/trends.php/ http://httparchive.org/trends.php/ [4] http://www.baqend.com/ http://www.baqend.com/ [5] http://www.btw-2015.de/res/proceedings/Hauptband/Wiss/Gessert-The_Cache_Sketch-165.pdf http://www.btw-2015.de/res/proceedings/Hauptband/Wiss/Gesser...
• HBGDH 11y ago
  QE MEDA
• 01GOD 11y ago
  Dashboard is essential. Thanks in advance for releasing a fully functional open source Parse dashboard.
• 01GOD 11y ago
  Dashboard is essential. Thanks in advance for providing an open source Parse dashboard today!
• piyushco 11y ago
  That's not good news for many of Parse users :( Here are some of the options to move on, - https://www.firebase.com/ https://www.firebase.com/ - http://www.kinvey.com/ http://www.kinvey.com/ - http://shephertz.com/ http://shephertz.com/
• 3lux 11y ago
  It would be nice to see the Go server that powers Parse.com's production servers. I recall in Gophergon 2015 there was a presentation on how they migrated from Ruby to Go. https://gophercon.com/talks/rebuilding-parse/ https://gophercon.com/talks/rebuilding-parse/
• parsehosting 11y ago
  We are gutted by this and so are our clients, so we are working to create a Parse Hosting service for both our apps and the other developers in the community. For more information checkout http://parsehosting.net http://parsehosting.net
• parsehosting 11y ago
  We are gutted by this and so are our clients, so we are working to create a Parse Hosting service for both our apps and the other developers in the community. For more information checkout http://parsehosting.net http://parsehosting.net
• lebnox 11y ago
  ShepHertz is providing seamless migration to App42. http://www.shephertz.com/parse-migration-app42.php http://www.shephertz.com/parse-migration-app42.php
• espitia 11y ago
  I've used Parse for all of my apps but I don't really understand what goes on between my client (iOS apps) and them. Reading on this would help a lot before trying to host the open source Parse Server by myself. Can anyone recommend tutorials/videos regarding hosting your own backend?
• csense 11y ago
  Can anyone explain to me what Parse actually is? Based on a quick read of https://parse.com/apps/quickstart#parse_data/mobile/android/native/new https://parse.com/apps/quickstart#parse_data/mobile/android/... this is basically a cloud-based key-value store, is that correct? And the value-add is basically that you can subscribe to stuff, and they did all the finicky cross-platform stuff to get it to work in mobile devices? And this is something that any competent developer could write in-house in a few days, but what they were selling it for is a lot cheaper than a few developer-days?
  • lazerwalker 11y ago
    That's correct, give or take a few other features. The selling point of Parse, at least to me, wasn't "this is complex or particularly high-quality engineering". It's "you want to bang out an MVP in a day. Awesome, we took care of giving you a server to shove shit on."
• alyssoncm 11y ago
  Parse it is a good solution for a quick app backend setup but I never realized build big things over there. To me the most important to me is no vendor lock-in I see as very important to have full control over what I'm developing. I started to use a great platform www.back4apps.com and Im happy with the results. I recommend it as a migration option
• leighmon 11y ago
  Facebook is impressing me.
• leighmon 11y ago
  Facebook is impressing me.
• jramps 11y ago
  How important is choosing a no lock-in MBaaS? Some considerations for backend users: http://www.anypresence.com/blog/2016/01/29/parse-shuts-down-reality-of-vendor-lock-in/ http://www.anypresence.com/blog/2016/01/29/parse-shuts-down-...
• ashutoshyadav 11y ago
  Seamless Migration from Parse to ShepHertz App42 http://www.shephertz.com/parse-migration-app42.php http://www.shephertz.com/parse-migration-app42.php
• ashutoshyadav 11y ago
  http://blogs.shephertz.com/2016/01/29/migrating-parse-pushnotification-app42-push-notification/ http://blogs.shephertz.com/2016/01/29/migrating-parse-pushno...
• ashutoshyadav 11y ago
  http://blogs.shephertz.com/2016/01/29/seamless-migration-parse-app42-backend-service/ http://blogs.shephertz.com/2016/01/29/seamless-migration-par...
• cloud170 11y ago
  I think someone posted this on another thread somewhere (and sorry I could not dig it back up). With MongoLab and Google Cloud Platform, I literally just re-specified the Parse App ID and Keys and got the Parser server up and running in matter of minutes: https://cloud.google.com/nodejs/resources/frameworks/parse-server https://cloud.google.com/nodejs/resources/frameworks/parse-s... Yes, with limitation on quite a few things now. But it's a good start. Next thing to explore is how to scale this thing out.
  • pseudobry 11y ago
    I put together that tutorial. Ping me @jmdobry (GitHub/Twitter) with questions. Also, https://gcp-slack.appspot.com/ https://gcp-slack.appspot.com/
• illuzyonist 11y ago
  We believe that not relying on another hosted BaaS solution is the best strategy. Just because of this we have created an API generation tool called API Plug that can benefit mobile and backend developers. You can export MongoDB from Parse right now. After that you can generate & download your own REST API source code in any language you need in minutes from https://apiplug.com https://apiplug.com Then you could deploy on your own server and have the full control of your backend.
• deleted 11y ago
  [deleted]
• ptz 11y ago
  I just found this: http://yourparse.com http://yourparse.com
  • dabodmb 11y ago
    There is even a kickstarter: https://www.kickstarter.com/projects/clintjohnson/parsenext-an-easy-migration-to-a-parse-style-platf?ref=nav_search https://www.kickstarter.com/projects/clintjohnson/parsenext-...
• chmaynard 11y ago
  Since this was clearly a Facebook decision, Facebook should have announced the shutdown on their own blog instead of humiliating the Parse team like this.
• conan311 11y ago
  Hi Guys, after a few hours of googling (trust me, I spent my whole Sunday being so pissed of at Facebook and researching alternatives to Parse.com), I arrived in this awesome page. I read a few comments below and it seems like I just found an oasis! With this open source project, do you guys think it would be still possible for an app to support FB sign in features?
• conan311 11y ago
  Hi Guys, I am trying to set up Parse Server and a Mongo DB locally on my mac. When I run Parse Server, I got this message "DATABASE_URI not specified, falling back to localhost". However, I did provide the DATABASE_URI. Probably I am so noob and didn't fully get it. The following is what I provided. Please advice me. var api = new ParseServer({ databaseURI: 'mongodb://localhost:27017/dev', cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js', appId: 'xxxx', masterKey: 'xxxx', });
• rezaqt 11y ago
  [Kii employee here] We've been getting many inquiries at Kii Corporation from Parse customers about migration. To get you started: https://en.kii.com/parse-migration/ https://en.kii.com/parse-migration/
• helloanand 11y ago
  Worth a read - The dirty little secrets of transitioning away from Parse https://medium.com/@suniltom/the-dirty-little-secrets-of-transitioning-away-from-parse-15522e2ce42d#.p4u5tp97h https://medium.com/@suniltom/the-dirty-little-secrets-of-tra...
• stefybiber 11y ago
  This thing has disturbed everyone who have hosted their apps on Parse platform, they are looking for an alternate solution. I am also one of them. I have already talked with various app development platform providers and check their platforms. I found Configure.IT as the nice solution compared to other platforms. Actually my 10 to 15 apps are on Parse. So I am bit worried about it. Now After checking all the solutions, Finally I reached to a decision. I also want to guide all the people who are passing through the same situation as I am passing. I have checked all the features and facilities provided by this platform and also talked with the authorized persons of this platform. Really a genuine one. So finally I have given the project of my apps migration to Configure.IT ( http://www.configure.it/ http://www.configure.it/ ) and they are doing it very nicely. Thanks to whole team. Thanks a lot.
• gabrielortiz 11y ago
  We built a Parse Replacement Service: http://nimbleparse.com http://nimbleparse.com
• gabrielortiz 11y ago
  We built a Parse Replacement Service: http://nimbleparse.com http://nimbleparse.com