With the renewal of the JS interface for daiquiri (toward react) we may ask our selves if we wish to simplify this aspect of daiquiri.
I a standard JS web application the structure is as follow:
graph LR;
USER-->JS;
JS-->REST;
REST-->ScienceDB;
Since we want to use this construct for the JS interfaces, I suggest to adapt the other interfaces to the same construct, creating a single point of access to the DB: the REST API.
IVOA SOAP, REST API, Direct DB access
Daiquiri accesses science data via three different ways. This mostly for historical reason.
With the renewal of the JS interface for daiquiri (toward react) we may ask our selves if we wish to simplify this aspect of daiquiri.
I a standard JS web application the structure is as follow:
Since we want to use this construct for the JS interfaces, I suggest to adapt the other interfaces to the same construct, creating a single point of access to the DB: the REST API.