Dalet Flex's Virtual File System

Dalet Flex has been designed from the ground up to be configurable and support as many vendor solutions and standards as possible. This versatility is brought about by ensuring all elements of Dalet Flex are pluggable and extensible. Dalet Flex’s Virtual Filesystem component is no exception. The Dalet Flex Virtual Filesystem has been designed to support a wide range of storage and file transfer protocols so that Dalet Flex can access files on a wide range of different storage devices. This abstraction layer means that file-based actions can seamlessly move files between different storage devices in different locations, whether that be local file-based storage, or cloud-based object storage.

Dalet Flex’s Filesystem has a built in abstraction layer which enables it to use a range of different storage and file transfer protocols. Examples include:

  • AZBS: For accessing files stored using Microsoft’s Azure Blob Storage.
  • File: For accessing files on local file mounts.
  • FTP: File Transfer Protocol.
  • FTPS: (also known as FTP-ES, FTP-SSL and FTP Secure) is an extension to the commonly used File Transfer Protocol (FTP).
  • GCS: For accessing files stored using Google Cloud Storage.
  • HTTP: Hypertext Transfer Protocol Overview.
  • HTTPS: Hypertext Transfer Protocol Secure.
  • SFTP: SSH File Transfer Protocol (also Secure File Transfer Protocol, or SFTP).
  • SMV: SMB/CIFS networking protocol.
  • S3: For accessing files in an Amazon S3 account.
  • WebDAV: Web Distributed Authoring and Versioning (WebDAV) is an extension of the Hypertext Transfer Protocol (HTTP).

Note: Please note that some of these protocols are read-only by design. The Dalet Flex Virtual Filesystem is not managed and configured directly. Storage resources are configured to support specific protocols and “mount” storage devices. File-based actions are then configured to access these storage resources.