This morning on #c9d9 we discussed Continuous Delivery for legacy applications.
Assuming your business did not start yesterday – you probably have some of those lying around: those applications that might be poorly understood, or poorly tested, that can be cumbersome or brittle, that may be difficult to update — but that somehow – still – just work.
This is the legacy code that keeps the lights on, but that you’re afraid to touch…
How do you deal with all your pre-DevOps applications?
Should you embark on a journey to ‘DevOps’ify your legacy applications? If so, how can you bring legacy code and technical debt into the fold – as part of your CD pipelines?
On the show, we discussed:
- How do you define Legacy?
- Should you poke that bear?
- What are some of the challenges doing CI and CD for legacy apps?
- What are some of the best practices to bring DevOps practices to legacy applications- where should you start, and how to go about it?
Watch the replay of the episode:
This episode features:
On the next episode of Continuous Discussions:
Join us on May 17, to discuss tips and best practices for offering a shared, consolidated, self-serve build/test cloud infrastructure and tool chain in your organization. (yes, it’s a mouth full, but it’s really interesting ;)).
This episode will feature:
Continuous Discussions (#c9d9) is a bi-weekly series. See all episodes here.
Latest posts by Anders Wallgren (see all)
- Continuous Discussions (#c9d9) Podcast, Episode 81: Gene Kim and the DOES17 Speakers #4 – Transformational Leadership - October 24, 2017
- Architecting Your App and Your Pipeline for Continuous Delivery – 10 DO’s for Successful DevOps - October 23, 2017
- Continuous Discussions (#c9d9) Podcast, Episode 79: Gene Kim and the DOES17 Speakers #2 – The Equifax Breach - October 6, 2017