How to modernize legacy web applications
Most firms have older web applications using legacy approaches; attempting to upgrade to a more modern standard is a unique challenge that means thinking about a wide array of radically different approaches. Josh Street explains how to modernize legacy web applications and walks attendees through some specific solutions for the challenges that can arise in these legacy systems.
Talk Title | How to modernize legacy web applications |
Speakers | Josh Street (AmWINS) |
Conference | O’Reilly Software Architecture Conference |
Conf Tag | Engineering the Future of Software |
Location | New York, New York |
Date | April 11-13, 2016 |
URL | Talk Page |
Slides | Talk Slides |
Video | |
A fundamental tenet of software architecture is that older systems must be modernized or replaced. Replacing applications can be a timely, expensive, and often unnecessary affair, leading many teams to pursue a strategy of upgrading existing applications. While often more cost effective, upgrading an application is among the most challenging technical efforts a team can undertake. Josh Street explores these challenges, which range from personnel-related issues (uptiering talent) to design issues (managing architectural mismatches and legacy technical debt), offering the information that will give your project the best chance for success. Josh explains how to modernize legacy web applications—from choosing the platform and technologies used to organizing the teams to executing and managing the project—and walks attendees through some specific solutions for the challenges that can arise in these legacy systems.