Domino uses Projects to organize work for data science and analytics teams. Projects help teams run experiments and improve code. Using Projects, you can manage data, code, artifacts, and user permissions.
Projects also help you follow best practices. They are flexible and can adapt to how your organization works. Projects support you through developing different analytical assets, from brainstorming ideas to launching them.
How you organize, store, and access files in Domino depends on your chosen project type. Domino has two types of Projects: Git-based Projects and Domino File System (DFS) Projects. Deciding on a Project-type will impact how you operate in Domino. We recommend using Git-based projects.
However, your organization may have policies that require you to use DFS or specific Git providers. Ephemeral and persistent disks on your platform’s containers can fill up. High disk usage or continuous high usage may affect service performance.
Git-based Projects
Git-based Projects let you choose a Git provider and a repository. Domino helps you sync your work, giving you control over saving versions. These projects use an external Git provider to store your files, offering better control and access to the provider’s features for a modern development experience.
Domino File System (DFS) Projects
Understanding how Domino manages files in a DFS repository is essential. These projects use the Domino File System (DFS) to store files. The workflow is similar to that of Git-based projects, but DFS does not have some features offered by external Git services.
The DFS automatically manages versioning with a Git server operated by Domino in the background. Domino also automatically generates specific files. Project Files and Work with Project artifacts have more information about these files and their management.
Combining code, data, and artifacts into one workflow is crucial for improving efficiency and driving innovation. All Domino Projects organize the related code, data, and artifacts needed to accomplish a Project’s goals. Projects can achieve better results and success by creating strong connections between these elements.
-
Code: Domino Projects have a Code repository that you can access from the left panel by clicking Code. DFS projects store artifacts directly in the Code repository.
-
Data: Data sources, Domino Datasets, and external data volumes can be accessed in the Data section of Projects. These tools are the preferred solutions for managing all your data needs. Each data offering operates independently from a Project to enhance collaboration and security.
-
Artifacts: Git-based Projects have an additional Artifacts repository accessible from the side panel. This is a DFS repository designed for storing artifacts that need to be kept outside the Git-based project.
Data files, like mapping dictionaries, are sometimes included in code or artifact projects. This works well if the files are small (less than 1 GB each) or if there are fewer than 50,000 files in total.
You can store data files in a repository. However, it’s best to limit the number of large files you store there. Repositories have storage limits, and exceeding these can slow down your future work. For details on storage limits and performance, talk to your Domino or external Git administrator.
-
Best Practices for Projects is a series of recommendations for effective data management in Projects.
-
Create Projects walks you through different options for creating Domino Projects.
-
Configure a Project contains information on the different configuration options for Projects.
-
Add Data to a Project explains how to discover available data in your deployment and add it to your project.
-
Collaborate on a Project teaches you how to collaborate on Domino Projects and share project outputs.