From Mainframe to Mainstream: A Case Study in Emberification
summary
Case study of modernizing a COBOL/DB2 mainframe reservation system into an Ember stack with concrete wins: migration uses Ember Data and Ember CLI deploy, over 40 web team members adopt Ember, upgrades move from 2.0 to 3.7 with minimal friction, a static marketing site becomes an Ember Publishing site serving 5,000+ pages, Jenkins build time drops from six hours to about three, and a working interactive deck plan feature proves the UI improvements actually ship.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:40What is a mainframe
- 1:30Why Terminals Suck
- 2:11Mythbusting Management
- 2:56Market Trends
- 3:19Community Driven Solution
- 5:30Conclusion
related talks
22mUsing Ember to Make the Seemingly Impossible Easy
25mThe Great Migration, Redesigning and Rewriting our App in Ember.js
22mUsing Ember to Make the Seemingly Impossible Easy
35mPanel: Ember – Why and Where?
28mModernizing a Massive Monolith
21mHow I Learned to Love Ember
01h 10mPanel: the future of Ember
24mBuilding a real ambitious application using Ember, Node & CouchDB