Samba
In our project we have decided to use Samba as a resource sharing service between the different teams. Although in our case we only use computers with Linux, we have chosen Samba because it offers us more possibilities in the field of compatibility, management and security, thinking not only of the present but also of a possible expansion of the system.
Why did we choose Samba?
Compatibility with other systems:
Although we only work with Linux systems now, Samba would allow us to easily integrate Windows computers if they are added at some point. In this way, we are not limited to a single platform and leave the infrastructure ready for the future. With NFS we could only work comfortably with Linux, so we preferred to bet on a more versatile option.
User control and permissions:
With Samba we can manage access to shared resources in a much more detailed way. We can define who can read, write or not access certain directories, and even integrate with authentication systems such as LDAP or Active Directory. This helps us maintain security and organization within the network.
Easy to use:
Another reason we chose Samba is because it is much more intuitive for users. Shared resources can be viewed directly from the file explorer (as if it were just another folder) and there is no need to do manual mounts or remember long commands. This makes day-to-day life a lot easier, especially if users don’t have advanced Linux knowledge.
Flexibility to share different types of data:
The project needs to share different types of information (administration documents, production files, backups, etc.), and with Samba we can configure independent shares, with permissions and routes adapted to each case. This allows us to have everything well separated and controlled.