{"id":192,"date":"2016-07-27T11:21:37","date_gmt":"2016-07-27T11:21:37","guid":{"rendered":"http:\/\/www.smash-ict.com\/?p=192"},"modified":"2017-02-24T14:06:08","modified_gmt":"2017-02-24T14:06:08","slug":"how-i-chose-my-parse-com-replacement-part-1","status":"publish","type":"post","link":"https:\/\/www.smash-ict.com\/nl\/blog\/how-i-chose-my-parse-com-replacement-part-1\/","title":{"rendered":"How I chose my Parse.com replacement (Part 1\/2): 5 things you should consider while choosing yours"},"content":{"rendered":"

Onze verontschuldigingen, dit bericht is alleen beschikbaar in het Engels<\/a>. Voor het gemak van de lezer, is de inhoud hieronder weergegeven in de alternatieve taal. U kunt klikken op de link om naar de actieve taal over te schakelen.<\/p>

<\/p>\n

This article was first published on July 20, 2016 as a guest post on the Codename One’s blog<\/a>.<\/em><\/h6>\n

\"Parse<\/a><\/p>\n

When I first read the announcement that Parse.com would shut down on January 28th 2017, I went from disbelief (it\u2019s probably an early April fool\u2019s joke) to rage (how could they do that?!) to sadness (oh no! it was a great service) and finally to utter confusion (where do I go from here and what do I do with my apps – <\/span>parse4cn1<\/a><\/span>, two <\/span>MVPs<\/abbr><\/a><\/span>\u00a0for clients and an upcoming rewrite of <\/span>Medex<\/a><\/span>\u00a0for which I was planning to use Parse.com as backend?). A few months down the line, a lot has happened such as the release of the open source Parse Server (yay!) and subsequently the Parse Dashboard. However, I still had to decide what do with my apps and I guess <\/span>you <\/span>have to as well.<\/span><\/p>\n

<\/p>\n

By now, the imminent shutdown of Parse.com must have hit home for you as well: You wish it was merely a bad dream but unfortunately it’s a stark reality. You’ve got just a few months left to migrate your existing apps and obviously do not want to face another shutdown. Nearly every major MBaaS<\/abbr> vendor is brandishing a banner that directly or indirect says “Parse.com let you down but you’re safe with us”. However, whom can you trust? Or maybe you should just host your own Parse Server? How about migrating away from anything Parse-like and settling for a completely different MBaaS<\/abbr>.<\/span><\/p>\n

In this post, I share some important points to consider while deciding on your replacement for Parse.com. In Part 2, I\u2019ll share how I applied these guidelines while migrating my own apps. This article is highly recommended for anyone who still has their apps on Parse.com or is contemplating using a Parse.com-like solution as backend for their (new) apps.<\/span><\/p>\n

\n

There Are Basically 3 Options<\/span><\/h2>\n

Don’t be intimidated by the long lists of Parse.com alternatives that you may have seen (for example, <\/span>this one<\/a><\/span>). Broadly speaking, all Parse.com alternatives fit into one of the following three categories:<\/span><\/p>\n

    \n
  1. Self-hosting<\/span><\/li>\n
  2. Parse Server hosting provider<\/span><\/li>\n
  3. Other MBaaS<\/abbr> (unrelated to Parse)<\/span><\/li>\n<\/ol>\n

    Let’s briefly consider these categories and give some examples.<\/span><\/p>\n

    1. Self-hosting<\/span><\/h3>\n

    Self-hosting comes in two flavors:<\/span><\/p>\n