An old dog is learning some new tricks. QNX has been around since the 80s, and the OS is getting a big update from BlackBerry.
For those not familiar, QNX began as one of the first OS’s using a microkernel architecture. As opposed to a traditional monolith kernel, a microkernel runs most system level events as “servers”, which can be turned off by developers as needed. This combined with being a real-time operating system made the OS a natural fit for embedded automative operating systems.
Now, QNX supports containers with the release of their QNX Hypervisor 2.0. This will allow developers to further fine tune how applications components interact with important safety systems. It seems like a natural extension for an OS entirely geared around minimal resource utilization, reliability, and compartmentalization.
Sadly, it doesn’t look like QNX will be running Docker on your car any time soon.
Larry Dignan Comments:
QNX Hypervisor 2.0 creates containers to ensure that any breach in one auto application can be contained. For instance, an issue in the infotainment system wouldn’t impact digital instruments with containers and application isolation.
Qualcomm Technologies is adopting QNX Hypervisor 2.0 for some of its digital cockpit applications. Qualcomm will use BlackBerry’s hypervisor for its Snapdragon 820A automotive platform.
- OpenFaaS: Serverless for Containers Made Easy - October 18, 2017
- Just Say No To KRACK - October 16, 2017
- One USB-C Hub to Rule Them All - October 16, 2017
- How to Accept Email Based Payments for Free as a Freelancer - October 13, 2017
- Satyamania: Windows Subsystem for Linux - October 13, 2017
- Technical Debt in the Age of AI - October 12, 2017
- The Origins of Premises - October 11, 2017
- Technical Debt Really Isn’t All That Bad – The On-Premise IT Roundtable - October 10, 2017
- E Tu Pluribus Networks UNUM? - October 9, 2017
- The Life and Death of Digital Re-Presentations - October 6, 2017