Maybe a stupid question - but I'm not a front-end guy, and my new front-end developer won't start for a couple of months.
I'm working on a solution for a microservices based data tool. Simply, this will be an interactive dashboard where users can add selected interactive widgets, from which they can select data to have a chart drawn. Sometimes the data needs to be sent directly from one widget to another widget - and sometimes an external microservice will need to do processing on the data before a new chart is drawn.
Based on this, I came up with the following schema (see image). I believe it makes sense to have the dashboard's API accept data from the external microservice, and then generate the interactive graph widget.
What I'm unsure of is; does it make sense to have the dashboard call it's own API for one widget to create another widget.
When I coded with Node.js, we did this all the time - but only with data and only in the backend (where one Node.js service just called another Node.js service - and they would talk back and forth via their APIs.)
Does this continue to make sense for a graphing frontend?
I am not following what the issue is. If you have a front end that needs server services then an API is required. This may comprise a single source or multiple.
Maybe outline what it is you think may be an issue.
From the outset I don't see any issues but I am not certain I understand the problem you are having.