ACERCA DE ESTE EPISODIO
In this episode of Continuous Delivery Office Hours, Tony Kelly chats to Bob Walker and Steve Fenton about modernizing legacy applications. Many teams and organizations face the decision on whether to modernize software that’s been running for years, and it’s no small undertaking. Listen to find out more about: Episode details You can also watch […]
Inglés
Estados Unidos
TRANSCRIPCIÓN 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
BUSCAR EPISODIOS ANTERIORES
Buscar episodios anteriores de Continuous Delivery Office Hours.
OTROS EPISODIOS EN ESTE PODCAST
To ensure software is deployable, teams must shift from manual testing to automated pipelines. Automation provides immediate feedback, captures institutional knowledge, and reduces long-term costs. Strategies like the Strangler Pattern help modernize legacy code for greater reliability. Listen to f…
Your branching strategy can support Continuous Delivery, or make it an impossible goal. Teams should assess the impact of how they branch on their ability to deliver software at all times, and that means there are some branching techniques that make software delivery more like walking in the dark t…
Your system’s architecture can support team autonomy, independent deployability, and independent evolution of components, or it can be a sticky mess. This episode looks at whether choosing a monolith or microservices fundamentally changes the crucial properties of your architecture. Listen to…
Tony Kelly hosts our first episode of Continuous Delivery Office Hours, with Bob Walker and Steve Fenton. In this episode of Continuous Delivery Office Hours, we ponder why prioritizing Continuous Delivery (CD) is essential for managing risk. We challenge the common instinct to reduce deployment fr…
While application code deployments have become highly automated and disciplined, database changes often remain manual, “folksy,” and prone to causing messy environment drift. Find out why databases require a uniquely cautious approach due to the severe risks of data loss and the impossi…
Descargo de responsabilidad: El podcast y el arte incluidos en esta página son de Future of Dev, que es propiedad de su propietario y no está afiliado ni respaldado por Listen Notes, Inc.
EDITAR
Gracias por ayudar a mantener actualizada la base de datos de podcasts.
