23.06.24

Getting Back on Track

Written by
Hanan Zakai
Published on
September 20, 2023
Read time
4
Category
Blog
Getting Back on Track

INTERESTING ARCHITECTURE TRENDS

Lorem ipsum dolor sit amet consectetur adipiscing elit obortis arcu enim urna adipiscing praesent velit viverra. Sit semper lorem eu cursus vel hendrerit elementum orbi curabitur etiam nibh justo, lorem aliquet donec sed sit mi dignissim at ante massa mattis egestas.

  1. Neque sodales ut etiam sit amet nisl purus non tellus orci ac auctor.
  2. Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti.
  3. Mauris commodo quis imperdiet massa tincidunt nunc pulvinar.
  4. Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti.

WHY ARE THESE TRENDS COMING BACK AGAIN?

Vitae congue eu consequat ac felis lacerat vestibulum lectus mauris ultrices ursus sit amet dictum sit amet justo donec enim diam. Porttitor lacus luctus accumsan tortor posuere raesent tristique magna sit amet purus gravida quis blandit turpis.

Odio facilisis mauris sit amet massa vitae tortor.

WHAT TRENDS DO WE EXPECT TO START GROWING IN THE COMING FUTURE?

At risus viverra adipiscing at in tellus integer feugiat nisl pretium fusce id velit ut tortor sagittis orci a scelerisque purus semper eget at lectus urna duis convallis porta nibh venenatis cras sed felis eget. Neque laoreet suspendisse interdum consectetur libero id faucibus nisl donec pretium vulputate sapien nec sagittis aliquam nunc lobortis mattis aliquam faucibus purus in.

  • Neque sodales ut etiam sit amet nisl purus non tellus orci ac auctor.
  • Eleifend felis tristique luctus et quam massa posuere viverra elit facilisis condimentum.
  • Magna nec augue velit leo curabitur sodales in feugiat pellentesque eget senectus.
  • Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti .
WHY IS IMPORTANT TO STAY UP TO DATE WITH THE ARCHITECTURE TRENDS?

Dignissim adipiscing velit nam velit donec feugiat quis sociis. Fusce in vitae nibh lectus. Faucibus dictum ut in nec, convallis urna metus, gravida urna cum placerat non amet nam odio lacus mattis. Ultrices facilisis volutpat mi molestie at tempor etiam. Velit malesuada cursus a porttitor accumsan, sit scelerisque interdum tellus amet diam elementum, nunc consectetur diam aliquet ipsum ut lobortis cursus nisl lectus suspendisse ac facilisis feugiat leo pretium id rutrum urna auctor sit nunc turpis.

“Vestibulum pulvinar congue fermentum non purus morbi purus vel egestas vitae elementum viverra suspendisse placerat congue amet blandit ultrices dignissim nunc etiam proin nibh sed.”
WHAT IS YOUR NEW FAVORITE ARCHITECTURE TREND?

Eget lorem dolor sed viverra ipsum nunc aliquet bibendumelis donec et odio pellentesque diam volutpat commodo sed egestas liquam sem fringilla ut morbi tincidunt augue interdum velit euismod. Eu tincidunt tortor aliquam nulla facilisi enean sed adipiscing diam donec adipiscing ut lectus arcu bibendum at varius vel pharetra nibh venenatis cras sed felis eget.

I recently had a meeting with the VP R&D of a leading Fintech company . In this type of meetings, we usually discuss technology challenges and business challenges that transform to…technology challenges. He told me that they were migrating their Angular FE to ReactJS, but the project was taking much longer than expected. It was supposed to last 3-4 months, but it was already in its 6th month and might not finish until the end of 2024.

I assured him that he was not alone or incompetent, he just encountered the "Startup success syndrome" (a term I coined). This phenomenon is common among startups that built their first product fast and lean. They get traction and customers (some of them even paying ones), and then they have to keep up with the demand for new features and support. The problem is that their quick and somewhat "dirty" solution was not designed for scalability and performance, and they had to compromise on quality for speed. Now, with every new customer, the technical debt increases.

I have seen many cases like this over the years, whether it was an Insurtech breaking a monolith into microservices, a cyber company migrating its FE using Micro Frontend architecture, or even a fintech Unicorn that had to migrated pipelines for hundreds of servers to prepare for its cloud migration. R&D leaders usually have three options: continue as usual, and hope for a compelling event or “compelling” a client that will push the project to the top of the priority list; assign an internal team that will dedicate 50-75% of their Backlog to the migration project, and deal with the pressure from the product team (good earplugs are recommended); or hire an external managed team that will focus on the migration project for 3-4 months, reduce the technical debt and get the release plan back on track.

One more personal observation derived from 25 years in the high-tech industry: the trigger will come eventually, so you should have some built-in indicators in your product development and delivery processes, for the potential "breaking points" and act before the crisis hits. You can find some more useful frameworks for anticipating and responding to a crisis in Rita Mcgrath's book: "Seeing Around Corners".