Based on Appian best practices in the documentation over the forum for Data Stor

We have all of our database calls SELECT, UPDATE, and INSERT as a call to a sub-process. Here are some advantages:
1. Helps with reusability. You will probably end up calling these processes multiple times across many processes.
2. If there are any changes at the database level, you have to just change the sub-process and republish it instead of having to republish the parent process. This is particularly useful when you are creating a new database/table. If you end up changing the design multiple times, you can just republish the sub-process.
3. It is lot easier for all of our developers to find where the database calls are. This is helpful for development and debugging.
4. You can have different developers work on the parent and sub-process resulting in faster application development.
5. We named our database related sub-processes with the table name as well. With hundreds of queries, this will increase the productivity of your developers as well.

Thank you Raj, I just want to calirfy the best to call these sub processes, is it using the sub-process node or call it using process-to-process message??

Appian wrote in the documentation the best way is to call it using process-to-process message, why is this?

Process to Process messaging allows to trigger events within a process, a process can contain many operations that are triggered by different events from type receive message (e.g. Update Student Table, Retrieve Student Record..Etc.).
Triggering a sub process smart service executes the from the start event of the sub process.

This is some great information. I've added parts of it the Data Stores page in documentation (forum.appian.com/.../Data_Stores

Thanks!