Evolving Your Architecture: Essential Steps and Tools for Modernization

Interview:

What's the focus of your work these days?

I am currently working on a finance institution modernization. My current focus is on ensuring the initiative succeeds. One key challenge I've encountered is balancing the wish of the team for a complete rewrite of the legacy system while adopting modern architectural styles without considering time to cost and business needs. The tendency toward big bang releases is another common challenge. This often leads to delays and increased risks. Through my work, I've learned the importance of promoting lean-based strategy for splitting the work (modernization in thin-slice) and meeting the business expectations while building a strong technical foundation that will guide the architectural evolution.

What technical aspects of your role are most important?

Modernization initiatives thrive on the ability to deliver working software frequently. Unfortunately, a limited understanding of iterative delivery methods can lead to cumbersome big bang releases. I possess the expertise to overcome this by promoting a thin-slice modernization approach, focusing on meeting business outcomes while building the technical foundation by leveraging engineering excellence – automated tests, frequent integration (CI), TDD, refactoring, clean code, pair programming, along with feature toggles and techniques such as transitional architectures, ensuring smooth and low-risk transitions from depending on the legacy system to the target state.
 

Another critical aspect is preventing past architectural issues from resurfacing. Through the application of evolutionary architecture principles and robust fitness functions (architectural tests, layered integrity, code static analysis, security checks, etc), I can guide the architecture's evolution without compromising its quality attributes and the agreed architectural principles. My deep knowledge in XP-based engineering practices further empowers the team to deliver value frequently and reliably. 

In essence, I bridge the gap between the on-the-ground development work and business goals, ensuring a high-quality software foundation that is built incrementally while delivering tangible business outcomes.

How does your InfoQ Dev Summit Boston session address current challenges or trends in the industry?

It's no secret that outdated technology and reliance on legacy systems hinder businesses from achieving their goals. While architecture modernization can be daunting and complex, the risks of inaction often outweigh the challenges of transformation. Unfortunately, some executive leaders defer modernization initiatives due to short-term priorities or a misunderstanding of the process itself. They might believe that simply updating technology will deliver benefits like agility, resilience, and growth. However, modernization is far more than a technical exercise. It encompasses a holistic approach that addresses funding allocation, prioritization, collaboration across teams, adoption of best practices, and fostering a culture of alignment.  Sadly, this broader perspective is often overlooked, leading to a high failure rate (nearly three-quarters) for legacy modernization projects.

How do you see the concepts discussed in your InfoQ Dev Summit Boston session shaping the future of the industry?

My session is a combination of pre-existing consolidated principles, practices and patterns – but many times seen and applied in isolation. Providing a broader view of the modernization journey – why, what, how and how to measure success – I want to broaden people's perspective not only in the process and how-tos but also in their role as senior practitioners in such a context.