---
title: "Comment by Roger Scroce on \"Move Large Volumes of Data Over REST with APEX & ORDS\" | Hashnode"
description: "Hi Jon, Just read your article. My preferred approach to this use case is PL/SQL. To avoid the sequential approach and the need to parse the response twice to t"
url: "https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/64c312fe3510fc491e1a9fe9"
---

[Discussion](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b)

Comment [Move Large Volumes of Data Over REST with APEX & ORDS](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b)

[Roger Scroce](https://hashnode.com/@RogerScroce)

[Jul 28, 2023](https://hashnode.com/posts/apex-ords-large-volumes-rest/6363b7f609fb89ffe67cc70b/comment/64c312fe3510fc491e1a9fe9)

Hi Jon, Just read your article. My preferred approach to this use case is PL/SQL.

To avoid the sequential approach and the need to parse the response twice to test for the next page of data, I use a 2 step approach:

1) call the rest api for a SINGLErecord to get the total record count.

2) build and execute ALL the api calls for individual pages in parallel. Parameterise the maximum concurrency in light of vendor rate limiting.

For my use case, Oracle CX implementations, this routinely achieves a 10X to 20X overall throughput.

100% Oracle and 100% free with Oracle ADB !
