JSON. Limits of the possible

Question:

Good day, uv. community. I'll get straight to the point:

  • What is the maximum amount of JSON data that can be taken from the server? Unlimited
  • What is the maximum amount of JSON data that can be taken from the server without harm to it and the client? Limited by iron
  • What is the maximum amount of JSON data that can be stored on the client?
  • What is the maximum amount of JSON data that can be stored on the client without harming the system? 2 GB ± …
  • How can I optimize the loading of a large amount of data (except Lazy loading)? Parallel download
  • How can you optimize the storage of large amounts of data on the client (caching, maybe Local Storage)?

Thanks in advance to all who respond.

UPD: JSON Compression algorithms – what can you say about it? Nonsense © @karmadro4


@rnd_d , I'm going to render the data, not all at once, of course, but in order not to waste time also loading this data, I need it in the form of Backbone.Collection on the client

@AlexWindHope , as far as I know, the number of parallel requests per domain is limited, in Opere, for example, the default is 16, but you can increase it to 128, I don’t know how things are in other browsers.

Answer:

I know that someone wrote a java software where they processed > 2GB of json (which led to the need to fix the JSON parser 4 java ). So you can use it to the fullest.

Considering that in most browsers JSON parsing is implemented at the native level, the speed is also at the level.

In general, if you are writing an application where it would be convenient to use the json data format, you should look towards noSQL document-oriented databases (mongoDB, couchDB).

Regarding the storage of more data – Local storage + a query of the form – has the data changed (if it has changed, of course, we pull new ones), if you wish, you can come up with something more complicated and interesting, but I don’t think that this makes sense, and if will be – that is a separate issue.

Scroll to Top