DiPhyx is an AI-enhanced, container-based platform that seamlessly enables data processing and computing across the cloud, local machines, and HPC environments. DiPhyx has three main components: Orchestrator, dxflow, and Dashboard.
It is an intermediary service that is used, both directly and indirectly, to connect customers with cloud service providers such as Amazon Web Services, Google Cloud, and Microsoft Azure. The main objective of the Orchestrator is to manage resources across all services offered by DiPhyx.
It is a distributed-computing technology developed by the DiPhyx team. It manages the deployed container using a core engine and multiple custom plugins. The distributed nature of the technology enables it to be deployed on the cloud or local devices (computers, HPC, etc). dxflow is accessible via an API and can be set up using a proxy.
It is a web-based graphical interface enabling users, teams, and companies to collaborate and access the services provided by Orchestrator and dxflow.
Scenario: Let's assume you have a computational pipeline (data, models, software) that you want to set up and execute on the cloud, and archive the data and results in a cloud storage space for future use.
It is a set of separate services that run on the Docker platform. These services are divided into two main parts: the core and the extensions.
Core, Mandatory
A Redis database that stores and retrieves all the data required by the other services.
Core, Mandatory
It is accessible through an HTTP web service interface. It processes requests and executes commands within the container environment. This service manages all administrative operations on the containers in the dxflow platform.
Core, Mandatory
A log storage service that acts according to the Syslog protocol and stores the logs of the containers running on the dxflow platform in the Redis database.
Extension, Optional
A proxy that processes all incoming requests in a secure environment and routes them to the appropriate service. This service also provides interactive sessions of the containers.
Extension, Optional
Accessible through an HTTP web service interface, it provides secure and easy access to files stored on the host disk. This service follows the TUS standard for file uploads with resume capability.
Extension, Optional
Accessible through an HTTP web service interface, it synchronizes the data bi-directionally between the host disk and the cloud storage. This service uses a queue for precise file synchronization.
Extension, Optional
Accessible through an HTTP web service interface, its responsibility is to process alarm configuration requests and then continuously monitor and notify when the alarm is triggered.
Yes, you can set up dxflow on any host computer, whether it is a cloud-based or local system. Additionally, you have the option to ignore any optional extensions and use only the core dxflow components if you do not require those extra features.
Yes, the processes of software development and debugging are readily available in DiPhyx. By using pre-defined software packages, you can increase the speed of development, and after performing the necessary debugging, you can proceed to transfer the programs to your production servers.