Build software for disruptive generic subdomains yourself

Author: Nick Tune

Question

When should we write software for generic domain ourself?

Short description

Sometimes dependencies are so generic that you don’t want to invest time in it and you want to buy them of the shelf: see outsourced-generic-subdomains

But if the market is potentially disruptive, then the bought system or SaaS solution might slow you down because of lack of innovation.

Examples

The company that created slack

Context

Use these at a strategic level when defining bounded context. When you want to seperate core domains from supporting and generic subdomains

Tags: designheuristic