Centralized E/E architecture is the move from many small, function-specific ECUs to a few powerful vehicle computers that host most application software. It is the structural change that makes software-defined vehicles practical.
Adding a feature historically meant adding an ECU, a supplier, a software stack and more wiring. Vehicles reached a hundred or more ECUs, each loosely coupled over CAN. The result was high wiring weight, fragmented software, slow update cycles and a security surface that was hard to reason about. Centralization attacks all four problems at once.
Centralized architecture moves application logic into one or a few high-performance computers running a real operating system, hypervisor and middleware. Features become software components scheduled on shared compute instead of dedicated boxes. This enables OTA updates, faster integration and reuse of code across vehicle lines and generations.
Consolidation does not remove safety and timing requirements; it concentrates them. The central computer and gateway must enforce freedom from interference between mixed-criticality workloads, preserve deterministic paths for safety functions, and keep diagnostic and security boundaries intact even though everything now shares hardware.
Few programs jump straight to a single computer. Most pass through domain controllers first, grouping powertrain, chassis, body and infotainment, then collapse those domains into centralized compute paired with zonal controllers for I/O. Legacy CAN ECUs remain for years, so the gateway keeps bridging old signal-oriented traffic into the new service-oriented core.