I’m a bit late to the party on this but the article fundamentally misunderstands DDD. DDD explicitly doesn’t concern itself with implementation details. It does

I’m a bit late to the party on this but the article fundamentally misunderstands DDD. DDD explicitly doesn’t concern itself with implementation details. It doesn’t have an opinion on DB servers, how you should partition data, etc. DDD is a way of modelling your business logic. Your domain doesn’t care about databases or servers, these are details at the edges of your application. If your domain does need to care about the details of how it runs on servers and databases, then perhaps DDD is not the right tool for the job.