Tag: legacy

Decomposition of a monolithic beast

Sit down in your chair and relax. Close your eyes and think about a system that you wouldn’t like to work on. What would it be like? Let’s check how much in common it would have with the one we have “inherited”.

  • Unsupported PHP 5.6
  • Unsupported Laravel 4.2
  • jQuery snippets used all over many different HTML files produced by Blade – Laravel’s templating engine.


That would be for the beginning. This system was supposed to be fed by an API and it partially was, however, during the most active development phase over 20 tables appeared in its own database, in most cases very “loosely related”, if at all. I believe that happened to speed up delivering short term functionality, but it actually illustrates the scale of the problem.


Strangler Pattern: How to strangle your legacy system

One of the most unavoidable things in software development is software aging. Technology, standards, patterns, and hardware are getting older and changing fast. One of the developer’s tasks is to maintain and keep the software up to date in order to make software age as slow as possible. Unfortunately, it’s easier said than done. New features and lack of resources leads to neglect of the software and makes it a so-called legacy system. Do you know how to save your system from becoming a legacy? Are you aware of the effects of having a legacy system? In this article, I answer these and some more questions.


We use cookies to enhance your user experience. By continuing to browse the site, you are agreeing to our use of cookies.
Read more