You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, PDF Keeper stores attachments within the database. While this approach has its advantages, it can lead to performance issues and database bloat, especially with a large number of attachments. Additionally, backing up large databases containing many attachments can be time-consuming and resource-intensive.
Proposal:
Introduce a configuration option that allows users to choose the storage location for attachments:
Database Storage: (Default behavior) Attachments are stored within the PDF Keeper database or other database like MySQL and SQL server
External Storage: Attachments are stored in a user-defined directory on the server. This option would improve performance and reduce database size, especially for large attachments or high-volume use cases.
Benefits:
Improved Performance: Storing attachments externally can significantly speed up data retrieval and reduce database load.
Reduced Database Size: Offloading attachments to external storage can free up valuable database space.
Enhanced Flexibility: Users can choose the storage option that best suits their needs and system resources.
Implementation Considerations:
Clear Configuration Options: Provide a user-friendly interface (e.g., in the application settings) to select the storage location.
Data Migration: Consider providing an option to migrate existing attachments to the chosen external storage location.
Security: Implement appropriate security measures for external storage, such as access control and encryption.
The text was updated successfully, but these errors were encountered:
Dear Sir
Currently, PDF Keeper stores attachments within the database. While this approach has its advantages, it can lead to performance issues and database bloat, especially with a large number of attachments. Additionally, backing up large databases containing many attachments can be time-consuming and resource-intensive.
Proposal:
Introduce a configuration option that allows users to choose the storage location for attachments:
Database Storage: (Default behavior) Attachments are stored within the PDF Keeper database or other database like MySQL and SQL server
External Storage: Attachments are stored in a user-defined directory on the server. This option would improve performance and reduce database size, especially for large attachments or high-volume use cases.
Benefits:
Improved Performance: Storing attachments externally can significantly speed up data retrieval and reduce database load.
Reduced Database Size: Offloading attachments to external storage can free up valuable database space.
Enhanced Flexibility: Users can choose the storage option that best suits their needs and system resources.
Implementation Considerations:
Clear Configuration Options: Provide a user-friendly interface (e.g., in the application settings) to select the storage location.
Data Migration: Consider providing an option to migrate existing attachments to the chosen external storage location.
Security: Implement appropriate security measures for external storage, such as access control and encryption.
The text was updated successfully, but these errors were encountered: