File Persistence
In Deyel, there are different options for storing files attached to entities and pages, depending on the specific needs and requirements of the application.
To define the type of repository to use, it is necessary to consider the required level of security, the necessary data volume, and whether the files are used on web pages.
Types of File Repositories
The types of repositories used for file persistence are the following:
File in Data Base
The files are stored in the database of Deyel and have a maximum supported size of 5Mb. This option allows files to be stored centrally along with the associated information.
Recommended for:
•Clients who want to keep all data, including files, within the database of Deyel.
•Environments where the goal is to centralize information and the files to be stored are few and small in size (less than 1 MB).
Advantages:
•The files are fully integrated with the other fields of the entity.
•No additional infrastructure is required if the database already manages other application data.
•Easy to manage at the database level through backups and replication.
Disadvantages:
•It is not suitable for storing large volumes of files, and each file must be smaller than 1 GB in size.
•Limited scalability compared to other storage options.
Typical use cases:
•Storage of small to medium capacity files, such as internal documents.
File in Amazon S3 Repository
Amazon S3 (Simple Storage Service) is a highly scalable and secure cloud storage platform. Files are stored in S3 buckets, making them easy to access, manage, and control. In Deyel, files are hosted in private buckets, accessible only from the platform environment. This solution allows for storing large files, making it ideal for applications that require high data volumes or large files.
Recommended for:
•Data that requires access only from Deyel considering the permissions modeled on the different objects. These files may include invoices, sworn statements, tax reports, etc., which require data security and protection.
•Organizations that use Amazon Web Services (AWS) and want to take advantage of its cloud storage infrastructure.
Advantages:
•High availability and scalability of storage.
•Advanced features: access control, data encryption, and automatic backup.
•Direct integration with other AWS services.
Disadvantage:
•In on-premise installations, an internet connection and an AWS account are required for the creation and management of dedicated buckets.
Typical use cases:
•Confidential files that require encryption and access control.
•Companies that need a robust, scalable storage solution capable of handling large volumes of data.
File in Amazon S3 Public Repository
Amazon S3 (Simple Storage Service) is a highly scalable and secure cloud storage platform. Files are stored in S3 buckets, making them easy to access and manage. In this case, the files are hosted in public buckets, freely accessible from the web without restrictions. This option allows for storage of large files and facilitates open access to them.
Recommended for:
•Public files used on websites, such as logo images, documents without sensitive data, or marketing materials.
Advantages:
•Easy access for users from the application without the need for authentication.
Disadvantages:
•Risk of unwanted exposure if permission settings are not managed properly.
•It is not suitable for storing sensitive or confidential data.
Typical use case:
•Images, marketing files, logos, or public documents that must be accessible from anywhere without restrictions.
File in File System (FileSystem)
In this mode, the file is stored directly in the installation's local file system. Instead of using a database or cloud service, files are stored in a directory on the local server or a shared location within the internal network.
This type of repository is only available in On-Premise installations.
Recommended for:
•Environments where storing files in the database or in the cloud is not desired.
•Situations where it is preferable to keep files on the local file system for performance reasons or specific infrastructure requests.
Advantages:
•Fast and direct access to files, especially in local environments.
•No additional infrastructure is needed if a file server is already in place.
Disadvantages:
•Not available in the Cloud version.
•It requires careful management to avoid file loss due to potential infrastructure failures.
Typical use cases:
•Applications that require direct and fast access to files in a controlled environment.
•Situations where data does not need to be accessible outside the local environment or does not contain sensitive information.
