As you see, the front-end part of the application is quite easy to set up: you can create a dashboard in less than an hour.
The true complexity hides in the logic of your project, namely how the data is transferred between the back end and front end. The time of implementation may vary from several days to weeks.
If you're creating a reporting module with the MongoDB database as a data source, I'd recommend you try the server-side connector released by the Pivot Table team. The only thing you need to do is to install this connector at your data layer. Its advantage is that it pre-processes the data from the database on the server side and sends already aggregated data to the component on your front end. Thus, if you have a lot of data, this saves your resources from being exhausted by client-side calculations.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
On average, how long did it take to develop this reporting module?. I am working on creating one with a NOSQL approach
As you see, the front-end part of the application is quite easy to set up: you can create a dashboard in less than an hour.
The true complexity hides in the logic of your project, namely how the data is transferred between the back end and front end. The time of implementation may vary from several days to weeks.
If you're creating a reporting module with the MongoDB database as a data source, I'd recommend you try the server-side connector released by the Pivot Table team. The only thing you need to do is to install this connector at your data layer. Its advantage is that it pre-processes the data from the database on the server side and sends already aggregated data to the component on your front end. Thus, if you have a lot of data, this saves your resources from being exhausted by client-side calculations.