Teradata Architecture

Basically Teradata architecture have three components..
those are:
1) PE(Parser Engine)
2)BYNET
3) AMP(Access Module Processor).

PE-parser Engine

• Heart of the Teradata.
• The Parsing Engines are perfectly balanced, with each having the capability to handle up to 120 users at a time.
• This could be 120 distinct users or a single user utilizing the power of all 120 sessions for a single application.
• That is why there are multiple PE’s in every Teradata system.
• Each PE has total command over every AMP.
• Each PE will take users SQL and do three things:

1.Syntax check - check the users SQL syntax.

2.Security Check - check the users ACCESS RIGHTS.

3.Plan - PLAN to satisfy the user request.

• The fastest plan is a Single-AMP retrieve.
• The second fastest plan is a Two-AMP retrieve.
• The next fastest plan will be all AMPs reading only a portion of the table, and The slowest plan is the full table scan. That is where each AMP reads every row they contain for a table.

AMP(Access Module Processor)

• Each PE rules them all because the rows of every table are spread across all the AMPs.
•  AMPs organize every table in separate blocks.
• PE passes the PLAN to the AMPs over the BYNET.
•  When a table is first created each AMP creates a table header on their disk.
•  When the table is loaded each AMP receives rows for that table that they and only they own.
• They carefully place the rows inside data blocks where they can easily be retrieved.

BYNET

• The PE comes up with a PLAN and passes the plan to the AMPs in steps over the BYNET.
• AMPs then retrieve the data requested by the PE and they deliver their portion of the answer set to the PE over the BYNET.
• BYNET provides the communications between AMPs and Pes.
• There are always two BYNETs for redundancy and extra bandwidth. AMPs and PEs can use both BYNETs to send and retrieve data simultaneously.