|
SDK |
API |
Self-hosted deployment |
Specificities |
- Deployment location: deployed to the purchaser's device side - Administrative privileges: Purchaser has full privileges - Data security: the buyer has absolute data security. - Restrictions: Restrictions on language, framework, platform - Offline |
- Deployment Location: Deployed to the server side of the API provider. - Administrative privileges: the API provider has full privileges - Data security: the buyer's data security is weak - Restrictions: No restriction on language, framework, platform - Online |
- Deployment location: deployed to the buyer's server side - Administrative privileges: Purchaser has full privileges - Data security: the buyer has absolute data security - Restrictions: No restrictions on language, framework - Offline |
Advantages |
- High security, local processing, integration of platform-related data will not be accessed - Fast response speed - High stability, stable function after docking, no quantity limitation. |
- Low maintenance costs, no server and server maintenance costs, can be charged according to the number of API requests, and if the API needs to be upgraded to fix bugs, the product can be upgraded online without affecting the user. - Low development cost, simple integration, can quickly verify the business model and user experience. - Low volume, API integration will not have additional resources to occupy the app capacity. |
- High security, local processing, integration related data will not be accessed - Fast response time - High stability, more stable functions after docking, no quantity limitation - Low development cost, simple integration, one-click deployment |
Disadvantages |
- High development costs, the development workload is relatively large API, but our SDK provides a standard version can speed up the integration speed - High maintenance costs, SDK upgrades to fix bugs, the product needs to be updated and upgraded simultaneously, and users can only use the product normally after it is released. - Large volume, SDK integration will take up a certain amount of app capacity. |
- Low security, the data need to go through the vendor's server, there may be a risk of collecting user data - Slow response time, need to upload the document to the server and then back after processing, long processing time - Low stability, affected by the network |
- High maintenance costs, requiring servers and server maintenance costs - Uncertain stability, depending on server performance |
Scenario |
- Applicable to complete functionality, including UI interaction-related - Suitable for customisation and extension, SDK is more flexible. |
- Applicable to independent module functions, such as watermarking, text splitting, merging, encryption, etc., for the need to interact with the functional limitations, such as annotation operations, content editing, etc. - Suitable for low budget, need to quickly verify the business model and market companies |
- Suitable for system integration - Clear requirements for data security - Customers who can only use the intranet, can not link to the extranet. |