Skip to content

Question: Are the parse limits lifted when hosting your own MongoDB #917

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
TylerBrock opened this issue Mar 8, 2016 · 14 comments
Closed

Comments

@TylerBrock
Copy link
Contributor

Before moving completely off of parse, but when MongoDB is hosted externally, are the usual Parse service limits in place?

For example the limits on counts, requests/sec, etc...?

@flovilmart
Copy link
Contributor

There are no limits in place in parse-server.

@TylerBrock
Copy link
Contributor Author

Right, of course, but I'm wondering about the intermediate stage. The stage when clients still hit api.parse.com but host your own MongoDB.

@mtrezza
Copy link
Member

mtrezza commented Mar 9, 2016

@TylerBrock The limit of API requests per second according to your current Parse.com plan seems to be still in place when you migrate to your own DB. As long as you keep using the Parse.com hosted API. You can see when you hit the limit in the dashboard and requests are not served.

@taufiq-husain
Copy link

How about the limits of queries? Usually parse limited queries of upto 1000 entries. Is this lifted in the open-source Parse server?

@mtrezza
Copy link
Member

mtrezza commented Mar 11, 2016

@taufiq-husain No, the limit restriction for query results of 1k objects exists also if you self-host your Parse Server. You can retrieve more objects through paging query.skip = 1000.

I assume the limitations are due to the original intention of Parse being a mobile BaaS. For mobile applications it makes sense to return a limited number of results to the client due to cellular network and mobile device resource limitations. The processing and filtering of data is supposed to happen server-side as much as possible, the client should have as little as possible and as much as necessary a) data to work with and b) data processing tasks. Depending on your use case maybe you can shift some logic to cloud code.

@otmezger
Copy link

otmezger commented Jun 1, 2016

@mtrezza will have the same limitations as well... In fact, parse.com had a limitation of 1000 elements per query and a max skip of 10000 if I'm not wrong, so that you could only get around 10.000 elements (in cloud code too). I hoped this will go away in self hosted parse-server.

@virtualtoy
Copy link

This is weird. This claims that self hosted parse-server doesn't apply limits. Just checked parse-server v.2.2.6 and query returned all 7.7k records

@mtrezza
Copy link
Member

mtrezza commented Jun 10, 2016

@virtualtoy Thanks for pointing this out. My statement back then was based on an actual test query. Did you set the limit parameter to >= 7.7k or not set it at all to fetch the 7.7k records?

@virtualtoy
Copy link

@mtrezza I set to 10000. By default it fetches 100 only

@adambarghouthi
Copy link

@virtualtoy where did you set it to 10000, because my default is 100 also

@TylerBrock
Copy link
Contributor Author

Use the limit() method on a Parse Query object.

@adambarghouthi
Copy link

oh straight in the code, thanks @TylerBrock !

@kylebakerio
Copy link

is this possible through the REST api?

@flovilmart
Copy link
Contributor

Yes, with the limit parameter

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

8 participants