Feedbaông chồng will be sent to infobandarpkr.com: By pressing the submit button, your feedbaông xã will be used to lớn improve sầu infobandarpkr.com products và services. Privacy policy.

Bạn đang xem: Obsolete là gì


In this article

Incrementally migrate a legacy system by gradually replacing specific pieces of functionality with new applications & services. As features from the legacy system are replaced, the new system eventually replaces all of the old system"s features, strangling the old system & allowing you lớn decommission it.

Context & problem

As systems age, the development tools, hosting công nghệ, & even system architectures they were built on can become increasingly obsolete. As new features and functionality are added, the complexity of these applications can increase dramatically, making them harder to lớn maintain or add new features lớn.

Completely replacing a complex system can be a huge undertaking. Often, you will need a gradual migration khổng lồ a new system, while keeping the old system to handle features that haven"t been migrated yet. However, running two separate versions of an application means that clients have sầu khổng lồ know where particular features are located. Every time a feature or service is migrated, clients need to lớn be updated lớn point to lớn the new location.

Solution

Incrementally replace specific pieces of functionality with new applications and services. Create a façade that intercepts requests going lớn the backkết thúc legacy system. The façade routes these requests either to the legacy application or the new services. Existing features can be migrated khổng lồ the new system gradually, và consumers can continue using the same interface, unaware that any migration has taken place.

Xem thêm: Nhập Gift Code Zing Me - Nhập Gift Code Zing Speed Mobile 2021 Mới Nhất

*

This pattern helps khổng lồ minimize risk from the migration, & spread the development effort over time. With the façade safely routing users to lớn the correct application, you can add functionality to the new system at whatever pace you lượt thích, while ensuring the legacy application continues to function. Over time, as features are migrated to the new system, the legacy system is eventually "strangled" and is no longer necessary. Once this process is complete, the legacy system can safely be retired.

Issues and considerations

Consider how lớn handle services and data stores that are potentially used by both new và legacy systems. Make sure both can access these resources side-by-side.Structure new applications và services in a way that they can easily be intercepted and replaced in future strangler fig migrations.At some point, when the migration is complete, the strangler fig façade will either go away or evolve inlớn an adaptor for legacy clients.Make sure the façade keeps up with the migration.Make sure the façade doesn"t become a single point of failure or a performance bottleneông xã.

When to lớn use this pattern

Use this pattern when gradually migrating a back-end application lớn a new architecture.

This pattern may not be suitable:

When requests lớn the back-over system cannot be intercepted.For smaller systems where the complexity of wholesale replacement is low.

Related guidance

Feedback