Refactoring Legacy Code with the Strangler Fig Pattern

Opens in a new windowOpens an external siteOpens an external site in a new window Large objects are a code smell: overloaded with responsibilities and dependencies, as they continue to grow, it becomes more difficult to define what exactly they’re responsible for. Large objects are harder to reuse and slower to test. Even worse, they cost developers additional time and mental effort to understand,

[tri-star]

複雑・巨大であちこちから参照されるクラスの分割やテーブルの分割といった変更をシステム無停止の条件かでリファクタリングする方法。