Architecture

Understanding the architecture of Tillered is crucial for realising its potential in optimising your network's bandwidth and performance. This section provides a high-level overview of the key components and how they interact to deliver seamless and efficient data transfers.

System Components

Tillered's architecture comprises several core components designed to work together to optimise data transfer and network performance:

1. Entry Node
2. Exit Node
3. Tillered Portal

1. Entry Node

The Entry Node is the initial point of contact within your network. It should be connected to your network, ideally on a separate network from the users or hosts that will benefit from Tillered. For example, in an office setting, you might have a main network for general use and a DMZ (Demilitarized Zone) network for the Tillered Entry Node.

• Role: Manages incoming traffic and optimises data packets before forwarding them to the Exit Node.
• Configuration: Automatically configures routes and provisions itself based on network changes.

2. Exit Node

The Exit Node is positioned as close as possible to your primary data transfer destination. For instance, if most of your data transfers are to the US, you would install an Exit Node on AWS in the us-east-1 region.

• Role: Receives optimised data packets from the Entry Node and routes them to their final destination efficiently.
• Configuration: Works in tandem with the Entry Node to ensure seamless data transfer.

3. Tillered Portal

The Tillered Portal is a web-based interface that allows you to manage and monitor your Tillered network.

• Role: Provides a centralised platform for configuring Entry and Exit Nodes, monitoring network performance, and viewing virtual IP assignments.
• Features: Includes dashboards for real-time monitoring, configuration tools, and detailed logs for troubleshooting.

Network Diagram

The following diagram illustrates the high-level architecture of a typical Tillered deployment:

Data Flow and Interaction

1. Initial Connection: User devices initiate data transfers which are routed through the Entry Node by the Firewall.
2. Data Optimisation: The Entry Node optimises the data packets using Tillered's congestion control and TCP session manipulation techniques.
3. Forwarding: Optimised data packets are forwarded from the Entry Node to the Exit Node over a secure and efficient network path.
4. Final Delivery: The Exit Node receives the optimised data packets and routes them to their original destination.

Scalability

• Multiple Exit Nodes: Easily add more Exit Nodes to your Tillered Network to expand coverage and improve performance across different regions.
• Automatic Configuration: Nodes automatically configure and re-provision themselves based on network changes, ensuring minimal manual intervention.

Conclusion

Tillered's architecture is designed to provide robust, scalable, and efficient network optimisation. By leveraging Entry and Exit Nodes and a powerful management portal, Tillered ensures your data transfers are fast, secure, and reliable.

For more detailed information or assistance with configuring your Tillered network, please contact our support team.