separating global and country-specific logics in large DDD application

Hi everyone

I'm using DDD for a global financial application (ASP.Net front-end WCF backend, NHibernate) that will be deployed to multiple countries (each having a completely separate installation and user base). All countries share some common logics and data (e.g. Account). But each country also requires some country-specific logics (e.g. extra values in enums, new properties, different logics for UK-only account types).

Any suggestions on how should I go about structuring my DDD stack (entities, domain services and repositories)? I certainly don't want all country-specific logics to end up becoming one big ball of mud so I need a way of keeping the codes for each country separate.

I've considered various techniques e.g. inheritance, composition, partial classes, complete fork...but none seems to stand out.

Are there any DDD techniques/patterns for tackling this specific kind of complexity? Those DDD examples I've read in books seem to assume universal / country-agnostic system.

Regards,
Joseph



------------------------------------