Re: Is IoC containers harmful for DDD?

In my opinion, business logic in a database is a recipe for disaster. Complex stored procedures are very handy when you need to perform lengthy queries involving lots of tables for a projection/view/dto. AND you have a VERY busy database (lots of transactions). Or retrieving a very complex set of data to needed for an aggregate. 

There's a reason why your domain is agnostic of your persistence layer. Unless you're still programmin in foxpro 2.6 :)





Sent from my iPhone

> On Dec 3, 2014, at 12:53 PM, Thomas Presthus [email protected] [domaindrivendesign] <[email protected]> wrote:
> 
> On Wed, 3 Dec 2014 17:33:23 +0000, "João Oliveira [email protected]
> [domaindrivendesign]" <[email protected]> wrote:
> 
> > If you are doing DDD with stored procedures owning business logic you
> are
> > doing it wrong.
> 
> Why is that? It's perfectly viable to implement a domain in your database.
> The problems come when you have business logic scattered in both database
> and other application code.
> 
> -- 
> 
> Thomas Presthus
> 
>