[Disccusion] Database(SQL) API design.

[kevinten10]

Goal

Design Database(SQL) API, like DB Mesh.

The current state API is essentially a key/value model API and does not support SQL query.

But:

• The database is so populor that almost every application is using it, we want to make the development as simple as we can.
• If we use state api or binding api, the database semantics are not very clear. There are some operation in dababase, but the operation can't be expressed clearly in state and binding api.
• In some database implements, such as PreparedStatement, we use it to void the Security Problem(SQL Injection).

Progress

We can first refer to some information and define a first version of the API.

Reference

mosn/layotto#101
dapr/dapr#3339
dapr/dapr#1339
dapr/dapr#3354

[kevinten10]

Refer to #dapr/dapr#3354

I already make a simple interface:

https://github.com/reactivegroup/cloud-runtimes-jvm/blob/feature/database/cloud-runtimes-api/src/main/java/group/rxcloud/cloudruntimes/domain/enhanced/DatabaseRuntimes.java

[kevinten10]

I added the first version of the database API to the enhanced module.

[kevinten10]

Hi，我这里有一个场景：关于混合云

因为实际生产环境不如想象中美好

现在，各个企业通常会基于开源的JDBC框架做二次开发，在自己的生产环境中使用X-JDBC，里面有一些针对私有云的定制化逻辑。（DB监控、分库分表 扥等）

这样一来，如果在多个云上使用通用的开源JDBC框架，意味着失去了在私有云中的各项功能，对企业而言是不可接受的。

企业希望的是：使用一套通用的SQL API，在私有云上运行X-JDBC，拥有定制化的功能，在公有云上使用JDBC，满足基础功能。