for having the best performance possible how should i serve data from the server ? Format CSV or JSON ? Use some sort of compressing algorithm between server and Flexmonster ? My back-end can be whatever i want : postgresql, elasticsearch, REST API, java, GO, etc…
Thank you for your question.
Being a client-side component, Flexmonster relies on resources available to the browser, which affects the loading time and the maximum size of the data that can be handled on every particular machine. This means that the client machine’s RAM determines how much data can be loaded at once, and CPU capabilities affect how much time is spent on the data analysis.
Aside from loading a JSON/CSV data set, Flexmonster provides the possibility to delegate data aggregation to the server-side, allowing to manage larder data volumes and use fewer browser resources. With this approach, a new query is formed on every change in the report (for example, expand, filter, etc.). This means that only the part of the data needed for the requested representation (expand, filter, etc.) is loaded at a time. You have the ability to load just part of the data necessary for the specified report. Depending on your data source type and use case, Flexmonster provides several options:
Please let us know if this helps, and if further questions arise – we will be happy to help.
As ElasticSearch is fast as hell i will choose JSON as format and ElasticSearch as database. I will use the datasource “subquery” property to select subsets of data from an index
Thank you for the update.
We are happy to hear that Elasticsearch works fine for you.
Should further questions arise, feel free to reach out.