By Scott Bils
Over the last several years we’ve all witnessed the disruptive nature of software. Startups have emerged that have transformed traditional markets – Tesla, Uber, AirBNB. We’ve also seen existing enterprises, such as GE and Ford take advantage of development and operational processes to speed innovation and drastically reduce time to value. However, many traditional application architectures and processes impede agility and impact innovation.
Historically, IT has offered a stack of technologies, including infrastructure, middleware and operating systems. These capabilities are usually sized, procured and planned far in advance of an application development initiative. Software development is complicated and has been based on slow, waterfall approaches to developing and maintaining monolithic applications. The downside to this approach is a time-to-market which can be unacceptable in today’s world, and fragile applications that aren’t resilient or easily scalable.
Determining how to address technical debt and modernize their application portfolio requires Applications teams to address several big questions including: