You can translate the question and the replies:

Exposing Microservice data to Data Virtualization Platform?

What is best practices when designing a Microservice from scratch that you know will need to expose (not ETL) data to a Data Virtualization Platform? I guess you could expose the DB, but then the MS would loose control of the data and agility would be harmed due to hard coupling to external product. /Björn
user
30-10-2020 10:12:53 -0400

1 Answer

Hi, Denodo does not claimed on how the Microservice should be designed in order to access it from the Denodo Platform. However, in general Microservices rely on JavaScript Object Notation (JSON) for transferring both requests and responses. Hence, you can also send data using REST, but the information ultimately ends up in JSON format. Since Denodo Virtualization Platform supports access the files in the [JSON](https://community.denodo.com/docs/html/browse/latest/vdp/administration/creating_data_sources_and_base_views/json_sources/json_sources#json-sources) format over the http data source, it is suggested to define the microservice to accept the request from a http client and return the reponse to the http client in JSON format. For more information, refer to the [HTTP Path](https://community.denodo.com/docs/html/browse/latest/vdp/administration/creating_data_sources_and_base_views/path_types_in_virtual_dataport/http_path#http-path) and [Authentication in HTTP Path](https://community.denodo.com/docs/html/browse/latest/vdp/administration/creating_data_sources_and_base_views/path_types_in_virtual_dataport/http_path#authentication-in-http-paths) section of the Virtual DataPort Administration Guide. Hope this helps!
Denodo Team
02-11-2020 07:16:39 -0500
You must sign in to add an answer. If you do not have an account, you can register here