Adopting DevOps Practices for Systems of Record – An Experience Report
summary
Systems of record like Siebel and mainframe get treated like regular code: source extracted into Git, Jenkins used for CI, Selenium/OpenUI for UI tests, a custom merge tool separates payload from metadata. Results include moved from 4 to 11 releases a year, a two‑week merge exercise cut to three days and overall cost roughly halved, and saved 3,300 days annually. Remaining problems: slow compiles, weak vendor APIs, unit test automation, and cultural/contracts resistance; Docker for COTS is still experimental.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:49Systems of Record - what is that?
- 3:21Two-Speed IT is an intermediate step, but you should not forget the enterprise applications Both digital and enterprise applications must move faster to keep pace
- 4:05The Legacy Complication...
- 4:52My view of DevOps
- 6:12Is it technology or culture that holds us back?
- 7:56Culture - A word of warning about maturity models
- 9:28Maturity models and what we can learn from Computer Games
- 10:29My Simplified View of the DevOps Software Supply Chain
- 11:413 Steps for your Systems of Record DevOps Journey It won't be easy, but the rewards are worth it!
- 13:46Why is COTS software is different Let's quickly compare your favourite web language with the usual COTS world
- 18:06All is good then with Systems of Record?!? ...This is where it comes undone (so far...) While we made lots of progress, there are still a few work in progress item
- 20:18Top 5 Takeaways
- 21:26Here is what I am struggling with
related talks
26mMainframe DevOps Transformation Case Studies
26mDevOps and Lean in Legacy Environments
30mTwo Amazing Mainframe DevOps Transformation Case Studies
43mThe Road to DevOps
44mBreaking a Monolithic Devops
27mTransforming Traditional Enterprise Software Development Processes
29mTaming the Hybrid Beast with DevOps
51mContinuous Deployment for a Billion Dollar Order System