Containerizations Vs Virtual Machines
summary
Compares automotive software realities: ADAS levels 0–5, big-data telemetry sent to AWS cloud, AI models that flag failing vehicles and enable over-the-air updates, and the hard constraint that full autonomy remains decades away (est. 40–50 years). Notes development cycles of 5–7 years, domain teams of thousands (radar teams ≈ 3–4k), widespread closed‑source stacks, CAN bus/ECU attack surface, and past recalls affecting millions (2009) that prove software can cause safety and recall events.
AI-written summary · about
chapters (11)
- 0:00DevOps in automotive intro
- 3:55Software vs hardware relation
- 7:03Automotive automation levels
- 10:40Data and big data role
- 13:57Car software dev challenges
- 17:35BMW cloud software experience
- 23:46Hardware vs software in cars
- 26:17Cybersecurity importance in cars
- 29:07Open vs closed automotive software
- 31:59Car hacking operations
- 34:12Safety tools in modern cars
related talks
44mConnected vehicle security: An AESIN tech talk on ADAS (advanced driver assistance systems)
46mAutomotive digital resilience and survivability
19mSecuring the future of mobility: Automotive threat modeling
46mRevolutionizing Automotive Software: DevSecOps, Functional Safety, and Open Source Sy...
26mAutomotive Cyber Security: Driving Business Transformation
43mConnected Cars - What could possibly go wrong?
41mThe Trajectory of Automotive Cybersecurity and the Role of AI
57mData on wheels