Home Ethernet Network Design: Database Normalization Diagram

Tech architecture infographic titled "Database Normalization" using PROTOCOL HANDSHAKE (numbered exchanges) adapted as a step-by-step data modeling handshake for a non-technical executive audience. Show a clean left-to-right flat diagram with labeled BOXES connected by ARROWS showing data direction and decision flow. Include these boxes even if conceptual: Browser — icon: monitor, name: "Business View", role: "Shows reports and data entry needs"; API — icon: server, name: "Application Rules", role: "Defines how data is created and queried"; Cache — icon: lightning database, name: "Reference Lookup", role: "Stores frequently used lookup values"; Queue — icon: message stack, name: "Change Requests", role: "Tracks schema updates and data fixes"; DB — icon: cylinder database, name: "Normalized Database", role: "Stores data in structured related tables". Add internal DB sub-boxes inside or beside the DB box: "Unnormalized Data — Repeating groups and duplicates", "1NF — Atomic values, no repeating columns", "2NF — Full dependency on whole key", "3NF — No transitive dependency", "Relationships — Primary key and foreign key links". Use numbered exchanges with arrows between components and DB normalization stages: 1) Browser to API labeled "Business fields and report needs"; 2) API to DB labeled "Source entities and attributes"; 3) DB internal arrow from Unnormalized Data to 1NF labeled "Split repeating groups"; 4) DB internal arrow from 1NF to 2NF labeled "Separate partial dependencies"; 5) DB internal arrow from 2NF to 3NF labeled "Move transitive attributes"; 6) DB to Cache labeled "Lookup tables and reference data"; 7) API to Queue labeled "Schema change request"; 8) Queue to DB labeled "Approved table update"; 9) DB to API labeled "JOIN query result"; 10) API to Browser labeled "Clean report data". If small protocol-style tags are needed, use technically accurate generic labels such as "REST metadata", "SQL DDL", "SQL SELECT", "JSON response"; do not imply literal network authentication if not relevant. Add a numbered legend 1-7 in English explaining lifecycle: 1. Collect business concepts and data fields. 2. Identify entities, keys, and repeating groups. 3. Convert to First Normal Form with atomic columns. 4. Convert to Second Normal Form by removing partial dependency. 5. Convert to Third Normal Form by removing transitive dependency. 6. Link tables with primary key and foreign key relationships. 7. Serve cleaner query results to the application with less duplication and better consistency. Add small callout notes for exec audience: "Goal: reduce duplication", "Trade-off: more joins", "Benefit: cleaner updates", "Not an audited reference architecture". Visual style: minimal flat, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Color palette: developer pink & teal with white background, dark charcoal text, soft gray connector lines, pink highlights for problems, teal highlights for improved normalized structure. Mood: calm, modern, explanatory, executive-friendly, uncluttered. Use clear hierarchy, spacious layout, rounded boxes, subtle shadows, simple icons, concise one-line descriptions in each box. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).