Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Pagination can be very limiting for backend processes - especially when combined with
The lack of aggregation forces us to fetch all the data to perform simple groupBy/count aggregations.
In the second case, the problem is that also running separate queries, or multiple queries in a single request, might take too long to run on Lambda.
We might get around this by structuring our data differently, though, or by moving away from AWS Lambda.
Right now, I just hack my way around it, which is ugly and lose-lose for both of us..
then, merge them all on post-response.. silly, right?
The only alternative I found is to bundle all tags in the build process as static json, and only fetch the diff (updated since build timestamp). I opted against, as it just feels like another hack, doesn't save much network bytes, and is another (slow) step in the build.
I did something similar to @oori . Probably not the best way to go about it, but it gave me the results I was looking for.