Very large HTTP request vs many small requests

by

Couple of considerations for choosing one big vs several small:

  • In the single request case, you can’t do progressive data processing as the data arrives; you need to wait for the full packet to arrive before you can do anything. If it fails, you need to start everything from scratch.
  • In the multiple requests case, you can do progressive data processing. However, you now have to consider the potential for multiple failures and how to recover from these.
  • Multiple requests incur overhead for each request. This is additional bandwidth you app will be consuming.
  • Some HTTP agents limit the number of concurrent requests to the same server, and you might need to do some logic to work around that.
  • Response compression will work better for the single request case.
  • Multiple requests won’t require you to allocate the full memory for your data. Granted, 640KB is not that big chunk of memory, so that might not be a big consideration for you, depending on how often you will allocate it.
  • In the case of early terminate of the process (either a Cancel button or the app is terminated or the browser navigates away from your page), the single request will still finish the full response download; however, for the multiple requests case, any request your code hasn’t started yet will not be executed.

Honestly, I wouldn’t be that worried about the last two and would base my choice on 1) is progressive data processing important; and 2) what your app tolerance is for failures and partial data.

More Related Contents:

  1. Does JSON syntax allow duplicate keys in an object?
  2. How do I get ASP.NET Web API to return JSON instead of XML using Chrome?
  3. How do I decode HTML entities in Swift?
  4. How do I modify fields inside the new PostgreSQL JSON datatype?
  5. Swift 4 Decodable with keys not known until decoding time
  6. My structures are not marshalling into json [duplicate]
  7. Excel VBA: Parsed JSON Object Loop
  8. pinterest api documentation [closed]
  9. Standardized way to serialize JSON to query string?
  10. How to use default serialization in a custom JsonConverter
  11. Gson optional and required fields
  12. Map JSON data to Knockout observableArray with specific view model type
  13. How to decode JSON with type convert from string to float64
  14. Json response download in IE(7~10)
  15. jq: Object cannot be csv-formatted, only array
  16. jqGrid returns blank cells
  17. How to receive JSON in a POST request in CherryPy?
  18. How to filter array of objects by element property values using jq?
  19. Why would you use a string in JSON to represent a decimal number
  20. Spark Row to JSON
  21. Swift 4 JSON Decodable simplest way to decode type change
  22. mvc 4 assembly reference missing for Json.Encode
  23. How to reuse Jersey’s JSON/JAXB for serialization?
  24. How can I deserialize an optional field with custom functions using Serde?
  25. Small Example of Jackson Scala Module?
  26. Merging JSONB values in PostgreSQL?
  27. HTTP 415 unsupported media type error when calling Web API 2 endpoint
  28. Post JSON to web in excel vba
  29. JQgrid total amount row
  30. How to extract all the keys in a JSON object with BigQuery

Leave a Comment