1# Data Sharing Through Silent Access 2 3 4## When to Use 5 6According to big data statistics, in a typical cross-application data access scenario, applications are started nearly 83 times on average in a day. 7 8To reduce the number of application startup times and improve the access speed, OpenHarmony provides the silent access feature, which allows direct access to the database without starting the data provider. 9 10Silent access supports only basic database access. If service processing is required, implement service processing in the data consumer. 11 12If the service processing is complex, use **DataShareExtensionAbility** to start the data provider. 13 14 15## Working Principles 16 17**Figure 1** Silent access 18 19 20 21- In silent access, **DatamgrService** obtains the access rules configured by the data provider through directory mapping, performs preprocessing based on rules, and accesses the database. 22 23- To use silent access, the URIs must be in the following format: 24 datashare:///{bundleName}/{moduleName}/{storeName}/{tableName}?Proxy=true 25 26 "Proxy=true" means to access data without starting the data provider. If **Proxy** is not set to **true**, the data provider is started. 27 28 The **DatamgrService** obtains the data provider application based on **bundleName**, reads the configuration, verifies the permission, and accesses data. 29 30 31## Constraints 32 33- Currently, only RDB stores support silent access. 34 35- The system supports a maximum of 16 concurrent query operations. Excess query requests need to be queued for processing. 36 37- A proxy cannot be used to create a database. If a database needs to be created, the data provider must be started. 38 39 40## How to Develop 41 42The URI must be in the following format: 43 44datashare:///{bundleName}/{moduleName}/{storeName}/{tableName}?Proxy=true 45 46For details about the development procedure and implementation, see [Sharing Data Using DataShareExtensionAbility](share-data-by-datashareextensionability.md). 47
