Inversion of control

Inversion of control

What's that inversion of control hype all about? We agree its a hype nowadays, but we've being involved with this principle as a way to create better applications for a long time before this hype, so please, don't think we're just another project trying to ride the tide.

Inversion of control is a design principle - and not a pattern! - which states that an entity should not actively obtain external entitites it needs to perform its work but instead expect that something else supplies these dependencies.

By using properly this strategy, the benefits will be a loosely coupled system, where components are interchangeable - provided that contracts are respected.

Other implicit consequences are:

• Reusability among different applications
• Testable software
• Better division of responsability