#domaindrivendesign — Public Fediverse posts

A year ago today, @roundcrisis, @ahl and I published the first episode of Stories on Facilitating Software Architecture & Design. Yesterday episode 27 went out. We've kept it going every two weeks since.

We didn't start it to publish content. We started it because the work engineers are being asked to do is changing, and most people are working that out on their own.

#SoftwareArchitecture #DomainDrivenDesign

Where should you put the anti-corruption/translation layer when migrating from a legacy system?

1. in the legacy
2. in new code
3. a dedicate translator service

A benefit of 1: fully encapsulate the legacy model and prevent it leaking

A benefit of 2: teams don't have to make PRs in multiple codebases for the same feature (when the ACL needs to change)

1/2

#architectureModernization #legacyMigration #softwareArchitecture #ddDesign #domainDrivenDesign

Where should you put the anti-corruption/translation layer when migrating from a legacy system?

1. in the legacy
2. in new code
3. a dedicate translator service

A benefit of 1: fully encapsulate the legacy model and prevent it leaking

A benefit of 2: teams don't have to make PRs in multiple codebases for the same feature (when the ACL needs to change)

1/2

#architectureModernization #legacyMigration #softwareArchitecture #ddDesign #domainDrivenDesign

Where should you put the anti-corruption/translation layer when migrating from a legacy system?

1. in the legacy
2. in new code
3. a dedicate translator service

A benefit of 1: fully encapsulate the legacy model and prevent it leaking

A benefit of 2: teams don't have to make PRs in multiple codebases for the same feature (when the ACL needs to change)

1/2

#architectureModernization #legacyMigration #softwareArchitecture #ddDesign #domainDrivenDesign

Where should you put the anti-corruption/translation layer when migrating from a legacy system?

1. in the legacy
2. in new code
3. a dedicate translator service

A benefit of 1: fully encapsulate the legacy model and prevent it leaking

A benefit of 2: teams don't have to make PRs in multiple codebases for the same feature (when the ACL needs to change)

1/2

#architectureModernization #legacyMigration #softwareArchitecture #ddDesign #domainDrivenDesign

Where should you put the anti-corruption/translation layer when migrating from a legacy system?

1. in the legacy
2. in new code
3. a dedicate translator service

A benefit of 1: fully encapsulate the legacy model and prevent it leaking

A benefit of 2: teams don't have to make PRs in multiple codebases for the same feature (when the ACL needs to change)

1/2

#architectureModernization #legacyMigration #softwareArchitecture #ddDesign #domainDrivenDesign

The cost of deferring some software architecture decisions can be significant.

As teams continue to build new features while awaiting clarity on an architectural direction, they make short-term choices or add avoidable complexity.

Example:

"[for this new feature] We are going directly to the big shared database rather than establishing clear interfaces.

...

1/2

#softwareArchitecture #architectureModernization #ddd #domainDrivenDesign

The cost of deferring some software architecture decisions can be significant.

As teams continue to build new features while awaiting clarity on an architectural direction, they make short-term choices or add avoidable complexity.

Example:

"[for this new feature] We are going directly to the big shared database rather than establishing clear interfaces.

...

1/2

#softwareArchitecture #architectureModernization #ddd #domainDrivenDesign

The cost of deferring some software architecture decisions can be significant.

As teams continue to build new features while awaiting clarity on an architectural direction, they make short-term choices or add avoidable complexity.

Example:

"[for this new feature] We are going directly to the big shared database rather than establishing clear interfaces.

...

1/2

#softwareArchitecture #architectureModernization #ddd #domainDrivenDesign

The cost of deferring some software architecture decisions can be significant.

As teams continue to build new features while awaiting clarity on an architectural direction, they make short-term choices or add avoidable complexity.

Example:

"[for this new feature] We are going directly to the big shared database rather than establishing clear interfaces.

...

1/2

#softwareArchitecture #architectureModernization #ddd #domainDrivenDesign

The cost of deferring some software architecture decisions can be significant.

As teams continue to build new features while awaiting clarity on an architectural direction, they make short-term choices or add avoidable complexity.

Example:

"[for this new feature] We are going directly to the big shared database rather than establishing clear interfaces.

...

1/2

#softwareArchitecture #architectureModernization #ddd #domainDrivenDesign

When modernizing your legacy systems, be careful not to automatically assume that the language your business and domain experts use is correct and should be reflected in your new architecture.

Their language might be influenced by your legacy systems and not an accurate reflection of the concepts in your domain.

Here is the kind of conversation I've had many times...

1/3

#ddDesign #domainDrivenDesign #softwareArchitecture #architectureModernization #archModernization

When modernizing your legacy systems, be careful not to automatically assume that the language your business and domain experts use is correct and should be reflected in your new architecture.

Their language might be influenced by your legacy systems and not an accurate reflection of the concepts in your domain.

Here is the kind of conversation I've had many times...

1/3

#ddDesign #domainDrivenDesign #softwareArchitecture #architectureModernization #archModernization

When modernizing your legacy systems, be careful not to automatically assume that the language your business and domain experts use is correct and should be reflected in your new architecture.

Their language might be influenced by your legacy systems and not an accurate reflection of the concepts in your domain.

Here is the kind of conversation I've had many times...

1/3

#ddDesign #domainDrivenDesign #softwareArchitecture #architectureModernization #archModernization

When modernizing your legacy systems, be careful not to automatically assume that the language your business and domain experts use is correct and should be reflected in your new architecture.

Their language might be influenced by your legacy systems and not an accurate reflection of the concepts in your domain.

Here is the kind of conversation I've had many times...

1/3

#ddDesign #domainDrivenDesign #softwareArchitecture #architectureModernization #archModernization

When modernizing your legacy systems, be careful not to automatically assume that the language your business and domain experts use is correct and should be reflected in your new architecture.

Their language might be influenced by your legacy systems and not an accurate reflection of the concepts in your domain.

Here is the kind of conversation I've had many times...

1/3

#ddDesign #domainDrivenDesign #softwareArchitecture #architectureModernization #archModernization