Come on, let’s get ready to RUMBLE!
Introducing first, the challenger, fighting out of the blue corner: It came with its open source stack and huge open source community. Ladies and Gentlemen, please welcome ‘Parse Cloud Code’
And now introducing the Titleholder, fighting out of the red corner, it came with its bunch of resources and features. Presenting the reigning, defending Serverless champion of the world: ‘AWS Lambda’
This guide aims to provide a set of good practices that will be helpful to beginners as well as expert developers who are starting to work with Back4App. If you are an experienced user of the platform, we recommend you to at least take a quick look at this tutorial, as it will surely help you find something informative that you didn’t know before.
Continuous Integration (CI) is the practice of merging all developer working copies to a shared repository several times a day. Its primary objective is to prevent integration problems, ensure quality and eliminate rework. It is meant to be used in combination with automated unit tests and continuous delivery so as, to reduce the breaking of code and to ensure that the software is always in a state that can be deployed to users, thus making the deployment process much quicker.
To enable all these features, it is necessary to use a CI server. For this tutorial, we will be using Travis CI , which is a hosted, distributed continuous integration service used to build and test software projects hosted on GitHub. Travis can be used to automate all sorts of tasks such as building, testing, and deploying software, with continuous integration and facilitation of technical aspects of continuous delivery.
The Internet of Things is coming closer to our daily lives each day more. With the advent of affordable, connected and small electronics, such as Raspberry Pi or other microcontrollers, we have the feeling that we can remotely control the entire world around us.
However, there is a difference between playing once or twice with electronics and building a reliable application to be actually installed in your home or even sold as a product. One of the features an IoT application must have is a solid Internet backend, in order to handle a high volume of requests, ensure scalability or work even under realistic connectivity.
It’s been a while since Parse closed down completely in Jan 2017. We take pride in the number of Parse.com users who have subsequently decided to put their trust in Back4App’s Parse Server Platform. We want to share with the community some of the lessons we’ve learned since this journey begun.
With Parse.com is due to close in a couple of days (28th January 2017) we’re very excited to announce an important new feature: Fast Migration.
Thanks to the forthcoming shutdown of the Parse server in January 2017 many developers wonder how they will keep their applications online from now on. This article focuses on the solution provided by Parse: the Parse-Server project. This is an open-source version of the Parse code, but with a few key differences.
To protect their data It’s extremely important for developers to migrate their apps to others solutions, such as Back4App .
This article will provide a comprehensive report explaining what is Parse Server, the history behind it, the most important contributors for the Parse Server community and the best alternatives for the Parse shut down. Reading this article, you will know:
If you still haven’t settled on an alternative to Parse, the premier cross-platform BaaS that will be shutting down as of January 28, 2017, you’re not alone. Fortunately, Parse has open sourced the code as Parse Server. Written in Node.js, Parse Server can serve the Parse API from any Node-enabled infrastructure.
