Ancestors

Written by Nick Tune on 2024-08-24 at 17:31

Architecture modernization anti-pattern: accessing another subdomain's data from the legacy system*

When building something new outside the legacy, you might be tempted to go direct to the legacy system to read/write data that you require (via the DB, CDC, or EDA).

If that data does not conceptually belong to the subdomain that is accessing it, you are breaking encapsulation: you are going via the backdoor to access another subdomain's data

1/3

[#]architectureModernization #ddDesign

=> View attached media

=> More informations about this toot | More toots from nick_tune@hachyderm.io

Written by Nick Tune on 2024-08-24 at 17:32

This becomes a problem when you modernize other subdomains. Your dependency on their legacy data persistence is an extra dependency they carefully have to avoid breaking and migrate.

Sometimes it's ok to do this as a short-term solution but it requires a high level of architectural maturity (to do it carefully and to repay the tech debt at the right time).

My recommendation is to...

2/3

=> More informations about this toot | More toots from nick_tune@hachyderm.io

Toot

Written by Nick Tune on 2024-08-24 at 17:32

....only allow a subdomain to access data that it conceptually owns from the legacy. Other subdomains should provide an interface to their data, even if it's a proxy to the legacy.

This approach certainly isn't perfect but it's a sensible default in my opinion.

• when done without very careful thought and consideration

3/3

=> More informations about this toot | More toots from nick_tune@hachyderm.io

Descendants