Apigee edge connectors for database without scripting

[#1]

Hi,

In Apigee documentation and videos everywhere they have said to use their in built policies rather than scripting as behavior of scripting with respect to performance can not be guaranteed all the time.

However on the other hand for connecting to database be it SQL or No-SQL, Apigee doesn't have any in built connectors which will automatically produce the api's and we have to rely on scripting like Node.js and in many posts Apigee folks have given an example of scripting for connecting to database

Major banks have their data on database and writing an application to expose data to be consumed by client API's via Apigee is not suitable in every scenario.

Does Apigee has any plans in future releases to build the connectors for database?

Example - IBM API Connect contains built-in support for Loopback which contains connectors for SQL as well as No-SQL databases as well as many advanced features and scripting is not required to connect to database.

[#2]

F5

[nagashree_b]

@Santosh Uplanchiwar

It is recommended that Apigee should be used as an API gateway, primarily to expose backend services as APIs. It is expected that the backend services do the heavy lifting of querying/updating the data, handling business logic etc. The API gateway layer should be kept light so that it doesnt add any delay in the processing time, at the same time you are securing your backend service/data from being vulnerable, as its not directly exposed to the consumers.

[juliansmiles]

You can using hosted targets. If you have npm modules available as connectors to your datasources, you can use them inside hosted targets i.e. nodejs apps