Tradeoffs Appian's cloud native Database (MariaDB) x Customer Database

In general, the close the database system is, the lower the latency. Then I think this is a question of the data protection policies of that client and the overall IT architecture guidelines.

In my experience, with Appian, we do not use many of the countless database features and if you have no very specific requirements then just go with the included DB.

In case you want/need direct access, Appian provides a way to do that.

As Stefan mentioned, it would be better to understand client/customer data protection policies.

Primary questions which may come up related to data encryption, Please find the below links if it helps, related to data base encryption

https://docs.appian.com/suite/help/24.1/Appian_Cloud_Database_Encryption.html

In case of data to be encrypted at a column level you can write your own plugin or their are  plugins available in app market which you can make use of it.

Hello [mention:0db15f06db76471fabc00d379f3e5906:e9ed411860ed4f2ba0265705b8793d05] 
The choice between Appian's built-in MariaDB and your client's own database depends entirely on their security requirements and project needs.

Appian's database offers a user-friendly, secure option ideal for simpler projects where a quick setup is crucial. However, if the project involves highly sensitive data or the client has a robust existing database infrastructure, using their own database provides greater control and flexibility for complex needs.

Ultimately, the best solution depends on your client's specific priorities.

Thanks for the help! [emoticon:c4563cd7d5574777a71c318021cbbcc8]

Another consideration could be data restoration.

In the cloud, everything is backed up at the same time (process and DB Data) by taking a instance snapshot. If you have an on-premise database, your DB backup could be slightly out of sync with the process data.