Modernizing Web Applications with Long Term Support
Experts from OpenLogic and Zend by Perforce discuss when to use long-term support while modernizing legacy systems. They talk about the timeline challenges of migrations and propose ways that long term support can be a useful tool for modernizing web applications.
This video is from the “Modernizing Legacy Web Apps: Strategies for a Seamless Journey” that aired on August 15, 2024.
To watch the full webinar, click here: https://ter.li/jo4a0g
Need long-term support before modernizing? Click the links below to explore LTS solutions and request pricing:
CentOS: https://ter.li/amyyb3
AngularJS: https://ter.li/rk1ayh
Bootstrap: https://ter.li/z5wnk1
About OpenLogic by Perforce:
OpenLogic offers end-to-end enterprise support for organizations using open source software in their infrastructure. With support for over 400 open source packages, guaranteed SLAs, and direct access to highly experienced Enterprise Architects, OpenLogic customers benefit from 24x7 ticket-based technical support, professional services, and training. Learn more at openlogic.com: https://ter.li/yx82q6
Follow OpenLogic on LinkedIn, Twitter, and don’t forget to subscribe to our YouTube channel for more videos on all things open source!
Transcript (lightly edited for clarity):
Yeshua: Like the slide says, especially with large code large code bases, LTS can become a necessity simply because it's going to take a long time for that modernization effort.
I’ve seen it with quite a few customers, where they thought a year’s time was plenty, so they put it off and didn’t really consider the migration until a year before end of life for the version. Then they realized that, wow, this is millions of lines of code. Their vendors have gone, and the community abandoned them, and they’re no longer being maintained. It takes a long time to replace those third-party components.
What they thought would just be a few months of migration and refactoring becomes a year and a half to two years. Not only that, but your team then focuses on that modernization effort pretty much one hundred percent of the time. Value-add features and things like that can fall to the wayside while they spend a year, two years, on the migration effort.
During that time, while you’re potentially stuck on that version, LTS could come in quite handy and give you that peace of mind through security patches. Your application is still secure, you can continue that modernization, but you don’t have to necessarily focus so heavily on it because you’re not racing that end of life. You’re able to spend that time and modernization investment over a longer period of time.
Matthew: Yeshua, being on the Zend side of things, is often looking at web applications and APIs. Tendai, on the OpenLogic side, is seeing another set of applications entirely. Tendai, do you have anything to add to this discussion here?
Tendai: Yeah. One of the things in terms of LTS is the timeline. Thinking of a particular big data project or big data stack, the infrastructure may be so large that it’s understood that modernization may take a number of years. One of things we’ve done or helped companies to do is really shoring up the existing application. By doing health checks, optimization, and ensuring the current legacy application is operating as efficiently as possible, we can provide some stability of that application while the modernization efforts are taking place.