Is Cloud the only option?
Before you dive in to Parse migration services for your existing application you need to decide if you really want to stick to a cloud solution. Primarily you need to remember one point – using BaaS (Backend as a Service) is a dicey option for any product if you are looking at long-term, this is basic business 101.
BaaS is a great solution for prototyping or as a MVP – you can develop your app rapidly and safely without having to worry about backend developer/ server code maintenance overhead.
Decide if you really want to stick to a cloud solution
First things first: using BaaS is a risky strategy for any product in the long-term. It’s business 101.
We recommend BaaS as a good solution for prototyping/MVP: you can ship your app fast and safe and not worry about backend developer/server code maintenance overhead. Vital infrastructure and backend code must be developed and owned internally. That is one of software development best practices and the Parse fiasco has demonstrated its importance. It is much more essential for items with officially proven traction and install base.
You may likewise consider moving your present setup to your servers – Parse distributed a module which permits. Keep in mind, in any case, this may conceivably bring about a few issues later on.
The choice is yours to take. Your last decision will rely on upon what phase of item market fit you are as of now at and what your long haul arrangements are. We emphatically recommend to the survey the extent of relocation before proceeding onward with the procedure. Acting in a surge is terrible in itself, however in the
event that you do it without counseling anybody, it could get worse!
Do a code audit
We trust that great code is a consequence of transparency, collaborations and awesome procedures. Thus, we consolidated pair coding and robotized tests as a feature of our work process. On top of this, we do code audits, both for internal and external projects.
We propose you do to the same with your task. Doing code audit not just gives you bits of knowledge into what's the issue with the application, additionally permits you to see the things from an alternate perspective.
On account of the Parse disaster, it will likewise help you with the choice procedure: Should I relocate to an open source Parse server? Should I rather pick different BaaS? Do I have to refactor everything? What amounts of conditions are there and how harmful will the procedure be? These are the essential inquiries that you have to reply.
Slow yet Efficient Migration:
You need to relax! Over all the years of software and mobile application development, many cloud services have gone out of business. We've generally figured out how to switch or refactor in time with no significant challenges (depend on it, in any case, littler issues will happen!). Simply keep in mind about doing a careful QA process amid and after the Parse migration process. The best news about this is the year has just begun and you have time till January 2017!
Crucial infrastructure and backend code should be owned and developed internally. That’s one of software development best practices and the Parse fiasco has proved its significance. It is even more important for products with already proven traction and install base.
You might also consider moving your current setup to your servers – Parse published a module which allows to do this. Remember, however, that this might potentially result in some problems in the future. Contact us if you’re not sure how to do this right.
The decision is yours to take. Your final choice will depend on what stage of product market fit you are currently at and what your long-term plans are. We strongly suggest to the assess the scope of migration before moving on with the process. Acting in a rush is bad in itself, but if you do it without consulting anyone, it’s even worse.
Do a code review
We believe that good code is a result of transparency, team efforts and great processes. For that reason, we incorporated pair coding and automated tests as part of our workflow. On top of this, we carry out code reviews, both for internal and external projects.
We suggest you do to the same with your project. Doing code review not only gives you insights into what’s wrong with the app, but also allows you to see the things from a different viewpoint. In the case of the Parse fiasco, it will also help you with the decision process: Should I migrate to an open source Parse server? Should I rather choose other BaaS? Do I need to refactor everything? How much dependencies are there and how harmful will the process be? These are the crucial questions that you need to answer.
Currently, we are carrying out such reviews for our Parse projects – both internally and for our clients – to assess the damage and make well thought out decisions about next steps.
Migrate it, slow and easy
Let’s recap. First, you need take a deep breath and relax. It is going to happen, whether you like it or not. Over the 7 years of software development we’ve witnessed dozens of cloud services go out business. We’ve always managed to switch or refactor in time without any major difficulties (make no mistake, however, smaller problems will occur!). Just don’t forget about carrying out a thorough QA process during and after the migration. The good news is you have 12 months to do this, as Parse will be switched off in January 2017.
How can you prevent such problems in the future? It’s perfectly normal and justifiable to use BaaS or other third party software, so don’t be afraid to do this. Yet, you need to ensure that you abstract out the dependency on such services.