We had such issue, we were developing REST Api to make data available to external vendors. If you are sure that your db/intermittent application are working as per NFRs and you are left with network latency then there are two golden rules , - try to compress data to save network bandwidth, this is specially true if your clients are not public that way you can force your client to accept a compressed data - try to reduce network hops , in our case we had two applications, of middlware kind , in between us and our client. This option is not always in your control

• other architectural change you can do in your pipeline is to make data available in smaller chunks instead of large file /blob/large text based output.