fast-paginate VS table-builder

There are ways to mitigate the (although not eliminate) the slowing down of offset/limit pagination in later pages. The technique is called a "deferred join" and it is most effective in MySQL. The basic idea is to paginate as little data as necessary, and then do a self-join to get the rest of the data for a single page.

You can read more about it here: https://aaronfrancis.com/2022/efficient-pagination-using-def... or here https://planetscale.com/blog/fastpage-faster-offset-paginati....

There are libraries for Laravel (https://github.com/hammerstonedev/fast-paginate) and Rails (https://github.com/planetscale/fast_page) as well!

Cursor based pagination is wonderful, but sometimes you're stuck with offset/limit for whatever reason. Might as well make it fast.

The PlanetScale team puts out incredible engineering content. Congrats on the release!

If you're using Laravel, there's a package that you can use to achieve the same effect: https://github.com/hammerstonedev/fast-paginate

In development you wouldn't use the build stage, you would just use the runtime stage and map your local files to your container using a volume. I normally configure all this using docker compose. You could still run things like composer through docker to ensure complete consistency between development and the build server (I normally do this with the help of bash scripts).