Single endpoint proceed a huge amount of operations or multiple endpoints each process single operation
N
NouranMahmoud
started a topic
almost 6 years ago
Hey Kinveyians,
I am trying to implement a web page which displays the name of specific collection which has the maximum number of specific data/record. but I calculate this operation for at least 15 collection all at one page.
I started to build an endpoint to process all the operations for all these collections and return a response with all the data. But, I found this will be a huge effort/cost on kinvey and It may take a long time to proceed that.
I thought about another solution which is to implement an endpoint for each collection single operation! .. by that I will make multiple requests to kinvey at least 15 request and each request be back to client with its specific result!.
The question here, is which is the better/preferred solution and the lower of the cost? ..
Best Answer
D
Damien Bell
said
almost 6 years ago
Nouran,
From our end: It doesn't really make much of a difference. We serve out large amount of data all the time.
From your end: It might make more sense to make it into multiple calls. Where business logic does have timeouts, it would be quite easy to run into a timeout where you are collecting a large amount of information before processing it.
From our end: It doesn't really make much of a difference. We serve out large amount of data all the time.
From your end: It might make more sense to make it into multiple calls. Where business logic does have timeouts, it would be quite easy to run into a timeout where you are collecting a large amount of information before processing it.
NouranMahmoud
Hey Kinveyians,
I am trying to implement a web page which displays the name of specific collection which has the maximum number of specific data/record. but I calculate this operation for at least 15 collection all at one page.
I started to build an endpoint to process all the operations for all these collections and return a response with all the data. But, I found this will be a huge effort/cost on kinvey and It may take a long time to proceed that.
I thought about another solution which is to implement an endpoint for each collection single operation! .. by that I will make multiple requests to kinvey at least 15 request and each request be back to client with its specific result!.
The question here, is which is the better/preferred solution and the lower of the cost? ..
Nouran,
From our end: It doesn't really make much of a difference. We serve out large amount of data all the time.
From your end: It might make more sense to make it into multiple calls. Where business logic does have timeouts, it would be quite easy to run into a timeout where you are collecting a large amount of information before processing it.
Does that make sense?
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstDamien Bell
Nouran,
From our end: It doesn't really make much of a difference. We serve out large amount of data all the time.
From your end: It might make more sense to make it into multiple calls. Where business logic does have timeouts, it would be quite easy to run into a timeout where you are collecting a large amount of information before processing it.
Does that make sense?
NouranMahmoud
Yes, it does, thanks.
-
How do I access query string values for GET and DELETE requests?
-
Basic Authentication in Business Logic
-
How do I cascade delete entities from related collections?
-
All BL failing with Violation Error
-
How do I send push notifications?
-
Whenever I try to query by _id, I get zero results
-
receiving SOCKETTIMEDOUT when requesting external http response
-
Unique Constraints on a collection column?
-
Need some help with grouping
-
Accessing Endpoint from Collection Hook
See all 342 topics