BYNET In Teradata – What are you

As we have talked about before, Teradata embraces the concept of SMP and MPP. Within the hardware context, there are two componets that build up this platform. The first if the Processor Node, this is responisble as the name implies for the data processing. This is mostly related to the concept of SMP. Within the realm of MPP, the BYNET is responsible for providing the interprocessor network that link together the components of the MPP system. This can take many forms, including broadcast, multicast, or point-to-point communication. The one that I had the most questions about was the BYNET thing.

The BYNET simply acts as the interconnect hub. Just think of it as the torso while the remaining SMP‘s are the limbs of the overall architecture. Most Teradata architects would poo-poo this description as it doesn’t embrace the concept of everything that the BYNET does but for the sake of my development it is the connector of a series of nodes (I am a Microsoft developer at the end of the day). Important thing to remember is that BYNET‘s in a multinode system can be load balanced and follow a standard TCP/IP protocol for inter-messaging. But, for the nodes to be aware of process oriented directions, load balancing is actually not required, just refines the process. At the end of the day, within all this, you end up with the overall MPP. If the BYNET is a single node, a virtual BYNET is used for simulation.