Skip to content

Parse hosting after April 28th - what does "deprioritise" mean? #1653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
neophob opened this issue Apr 27, 2016 · 6 comments
Closed

Parse hosting after April 28th - what does "deprioritise" mean? #1653

neophob opened this issue Apr 27, 2016 · 6 comments

Comments

@neophob
Copy link
Contributor

neophob commented Apr 27, 2016

Hi

I read that if the Parse DB isn't migrated until the April 28th the parse application gets deprioritised ("We recommend migrating your database by the end of April, but migrating your application logic to Parse Server can wait a few more months. If you have migrated your database by April 28th, we won't deprioritise your application server").

What does "deprioritise your application server" effectively means? Is the request rate capped? DB slow? Get the application shut down before next january?

@bohemima
Copy link
Contributor

#1639 (comment)

@neophob
Copy link
Contributor Author

neophob commented Apr 27, 2016

Thanks @bohemima - I saw those comments:

As I've understood Parse will prioritize migrated instances after this deadline but will not shut anything down. I read it as your QPS performance might take a hit or something similar. I found #1106 (comment) from Drew

you can keep your app server on Parse.com after you've migrated your database. We recommend migrating your database by the end of April, but migrating your application logic to Parse Server can wait a few more months. If you have migrated your database by April 28th, we won't deprioritise your application server

But I'm still not 100% sure what it means, especially "but migrating your application logic to Parse Server can wait a few more months." - does this means db migration can't wait? What are the concrete impacts?

@FridaySG
Copy link

I think what it means is that simply applications with migrated databases will have resource priority over those without, and would probably only be noticed when Parse is experiencing heavy traffic. I don't think it means they will intentionally slow it down. I could be wrong though, Parse reps have the final word.

@drew-gross
Copy link
Contributor

Duplicate of #1106 and #1639 (comment)

@araskin
Copy link

araskin commented Apr 27, 2016

So can we have that confirmed from some one at Parse? What does 'reprioritize' mean?

@hramos
Copy link
Contributor

hramos commented Apr 27, 2016

Closing as duplicate of #1639. See my comment.

@hramos hramos closed this as completed Apr 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants