Geek Answers Handbook

Should graph data be generated at the trailing end or trailing end?

Recently, I discussed at the office the question of whether to provide graph data obtained using our internal back-end api, or to provide general data and divide it into a graphic format in the interface. Here are the main notes that I collected from my team:

Foreground Benefits:

  • Data is transferred from the backend in a common format.
  • Since the data is in a general form, you can use any graph rendering interface. Provided that the parser method is written

Front end:

  • A parser must be enabled on the front-end to convert the general data into actual graph data.

Back profiles:

  • The data can be provided in the correct format, which negates the need for parsing on the front panel

Back end cons

  • Blocks which graphics library we can use.

This seems to be either a / or script, but I wanted to ask a question in order to get any other possible information.

By back-end, I mean the REST API and the interface I am for web applications (Javascript).

+4
source share
2 answers

To add your own list, you can take into account the following.

  • Serialization and data management in the background uses more RAM, since all your data is first loaded into memory.
  • , REST API. API.
  • front-end , , ram "graph". , .
  • , / ( ). , - . , , /.

, .
PS

back-end REST API / .

JS , - , .

+6

, . ?

0

More articles:


All Articles