January 19, 2038 – What can Enterprise Architects and Business Architects do to assist the Enterprise in addressing this catastrophic risk?
On January 19, 2038, at 03:14:07 UTC, older 32-bit systems will hit the “Year 2038 bug,” risking crashes, data corruption, and broken security and financial processes as their clocks suddenly jump back to 1901.
On January 19, 2038, at 03:14:07 UTC, older 32-bit systems will hit the “Year 2038 bug,” risking crashes, data corruption, and broken security and financial processes as their clocks suddenly jump back to 1901.
Watch to learn how to find these hidden time bombs in your systems and applications, migrate to 64-bit time safely, and put governance and testing in place so 2038 is just another date on the calendar. For 2038, the priority is to inventory 32-bit time dependencies, treat them as architectural risk, and integrate upgrades into normal refresh cycles rather than waiting for a last-minute scramble.
Keep learning with BACOE
Explore 195 articles, videos, podcasts and practical resources in the BACOE Valuable Content Library to support your business architecture work.
