Hub Mesh

What is Hub Mesh?

Hub Mesh represents our forward-looking vision for interconnected instant3Dhub instances, enabling seamless sharing of resources and computational capabilities across a network. It sets the stage for a transformative approach to collaboration, optimizing performance, cost, and operational efficiency within a distributed “mesh.”

With the release of instant3Dhub 3.10, we are proud to introduce 3D Space Transfer, the inaugural feature of Hub Mesh. This feature streamlines access to resources across multiple instant3Dhub instances, enhancing offline data availability and reliability in low-connectivity scenarios while maintaining robust authorization control.

This is just the beginning. The broader vision for Hub Mesh includes unlocking capabilities such as dynamic load balancing, and access to linked data resources. By integrating these features, Hub Mesh will evolve into a robust framework for distributing workloads and managing resources across instant3Dhub instances, driving efficiency and scalability in complex 3D data workflows.

What is Hub Mesh 3D Space Transfer?

Hub Mesh 3D Space Transfer is the first feature of the broader Hub Mesh Vision, designed to enhance collaboration and data accessibility across connected hub instances. It allows one hub to securely access and transfer resources in form of a caches managed by another hub, facilitating resource usage without duplicating data sets or compromising security.

Use Case 1: High-Reliability Data Access in Manufacturing

Companies with critical operations, such as manufacturing facilities, can leverage Hub Mesh 3D Space Transfer to ensure uninterrupted data access. By transferring caches from a central hub connected to the main data management system to a local instant3Dhub instance within the facility, operations can continue smoothly even if the connection to the central instant3Dhub instance is lost. This setup guarantees that essential data is always available on-site, minimizing downtime and maintaining production efficiency despite any network disruptions with the central hub.

Example: In a manufacturing facility, line workers are dependent on consistent data availability during their shift. To ensure availability in the manufacturing facility a 3D Space is prepared with the relevant data for the day. Via the 3D Space Transfer all relevant caches of resources that lie in the central company infrastructure are now available in the manufacturing facility making sure operations are running smooth.

Use Case 2: Optional Cross-Hub Authorization of Resources

3D Space Transfer provides companies with the option to simplify data access in coordination with their IT Security concepts. By reducing the need for individually registering and granting permissions—a process that is often complex, time-consuming, and, more importantly, keeps employees from working with the data they need to achieve their best results—this functionality streamlines data access and authorization. Authorized personnel can transfer entire 3D Spaces to another instant3Dhub instance, allowing teams to collaborate more efficiently while still adhering to security protocols.

Example: In manufacturing facilities, line workers often lack direct access to critical 3D data not because they shouldn’t view it, but because managing access for each employee is challenging due to high staff turnover and frequent crew changes. Traditionally, granting access involves cumbersome procedures that can delay operations. With 3D Space Transfer, the facility lead - authorised in coordination with the security concept - can transfer the required 3D Space directly to the workers’ infrastructure. This approach give companies the option to simplify data access, enables employees to perform their tasks effectively, and maintains compliance with the organization’s security policies.

How does 3D Space Transfer work?

Hub Mesh 3D Space Transfer allows information in 3D Spaces to move seamlessly and securely between connected instant3Dhub instances. Here’s how the process works:

Data Flow and Synchronization between instant3Dhub instances

  1. When a client connected to Hub A requests resources managed by Hub B, the system initially proxies the resources from Hub B to Hub A.

  2. Upon triggering the 3D Space Transfer using the transferSession() function or ResourceAPI, the system begins downloading the resources available at the time from Hub B to Hub A.

  3. While the download is in progress, resources are still proxied.

  4. As soon as a resource is fully transferred, it becomes available locally on Hub A. Any changes made to the 3D Space on Hub B require a new transfer to be initiated.

Authorization and Access Control

Authorization settings are configured through the datapool configuration in the values.yaml file. Each entry in the datapool section describes required headers or cookies when accessing data. Additionally, an authBehavior section specifies how to treat access based on whether the data belongs to a mesh member or was transferred over. This allows disabling or changing authorization behavior for transferred data. See the default values.yaml for more details.

Resource Integrity and Error Handling

  • Each transfer step retries up to five times. If a step fails after five retries, the specific resource is marked as being in an error state.

  • Kubernetes logs from the i3dhub-transfersvc pods can be reviewed for details. The transfer process involves multiple steps: resolving links, waiting for a transfer to be ready, refreshing signatures, waiting for download, or backing off from a failed step. Finding the cause of a failed step requires analyzing logs of all running pods as each step is randomly assigned. Failures are logged with error log level.

Did you find this page useful? Please give it a rating:
★ ★ ★ ★ ★
Thank you for rating this page!
Any issues or feedback?
What kind of problem would you like to report?
Please tell us more about what's wrong: