鏈敯鎬濆煙Type-R 姊﹀够鐨勭鏈哄厷(涓?

Dependency Inversion Principle(DIP)

It is a part of SOLID^[About] which is a part of OOD and was introduced by Uncle Bob. It is about loose coupling between classes(layers...). Class should not be depended on concrete realization, class should be depended on abstraction/interface

Problem:

//A -> B
class A {
  B b

  func foo() {
     b = B();
  }
}

Solution:

//A -> IB <|- B
//client[A -> IB] <|- B is the Inversion 
class A {
  B ib

  func foo() {
     ib = B()
  }
}

Now A is not depended on B(one to one), now A is depended on interface IB which is implemented by B, it means that A depends on multiple realization of IB(one to many)

[DIP vs DI vs IoC]

Dependency Inversion Principle(DIP)

It is a part of SOLID^[About] which is a part of OOD and was introduced by Uncle Bob. It is about loose coupling between classes(layers...). Class should not be depended on concrete realization, class should be depended on abstraction/interface

Problem:

//A -> B
class A {
  B b

  func foo() {
     b = B();
  }
}

Solution:

//A -> IB <|- B
//client[A -> IB] <|- B is the Inversion 
class A {
  IB ib // An abstraction between High level module A and low level module B

  func foo() {
     ib = B()
  }
}

Now A is not depended on B(one to one), now A is depended on interface IB which is implemented by B, it means that A depends on multiple realization of IB(one to many)

[DIP vs DI vs IoC]

Dependency Inversion Principle(DIP)

It is a part of SOLID^[About] which is a part of OOD and was introduced by Uncle Bob. It is about loose coupling between classes(layers...). Class should not be depended on concrete realization, class should be depended on abstraction/interface

Problem:

//A -> B
class A {
  B b

  func foo() {
     b = B();
  }
}

Solution:

//A -> IB <|- B
//client[A -> IB] <|- B is the Inversion 
class A {
  B ib

  func foo() {
     ib = B()
  }
}

Now A is not depended on B(one to one), now A is depended on interface IB which is implemented by B, it means that A depends on multiple realization of IB(one to many)

DIP + DI

[Dependency Injection(DI)]

• [Factory Method]
• Service Locator
• [IoC-container(framework)]

More complex example

Dependency rule in multi layer/module structure

Pseudocode:

interface InterfaceInputPort {
    func input()
}

interface InterfaceOutputPort {
    func output()
}

class A: InterfaceOutputPort {

    let inputPort = B(outputPort: self)

    func output() {
        print("output")
    }
}

class B: InterfaceInputPort {
    let outputPort: InterfaceOutputPort

    init(outputPort: InterfaceOutputPort) {
        self.outputPort = outputPort
    }

    func input() {
        print("input")
    }
}

[DIP vs DI vs IoC]

Dependency Inversion Principle(DIP)

It is a part of SOLID^[About] which is a part of OOD and was introduced by Uncle Bob. It is about loose coupling between classes(layers...). Class should not be depended on concrete realization, class should be depended on abstraction/interface

Problem:

//A -> B
class A {
  B b

  func foo() {
     b = B();
  }
}

Solution:

//A -> IB <|- B
//client[A -> IB] <|- B is the Inversion 
class A {
  B ib

  func foo() {
     ib = B()
  }
}

Now A is not depended on B(one to one), now A is depended on interface IB which is implemented by B, it means that A depends on multiple realization of IB(one to many)

[DIP vs DI vs IoC]

Dependency Inversion Principle(DIP)

It is a part of SOLID^[About] which is a part of OOD and was introduced by Uncle Bob. It is about loose coupling between classes(layers...). Class should not be depended on concrete realization, class should be depended on abstraction/interface

Problem:

//A -> B
class A {
  B b

  func foo() {
     b = B();
  }
}

Solution:

//A -> IB <|- B
//client[A -> IB] <|- B is the Inversion 
class A {
  B ib

  func foo() {
     ib = B()
  }
}

Now A is not depended on B(one to one), now A is depended on interface IB which is implemented by B, it means that A depends on multiple realization of IB(one to many)

DIP + Dependency Injection(DI)

[Dependency Injection(DI)]

More complex example

Dependency rule in multi layer/module structure

Pseudocode:

interface InterfaceInputPort {
    func input()
}

interface InterfaceOutputPort {
    func output()
}

class A: InterfaceOutputPort {

    let inputPort = B(outputPort: self)

    func output() {
        print("output")
    }
}

class B: InterfaceInputPort {
    let outputPort: InterfaceOutputPort

    init(outputPort: InterfaceOutputPort) {
        self.outputPort = outputPort
    }

    func input() {
        print("input")
    }
}

[DIP vs DI vs IoC]

Dependency Inversion Principle(DIP)

It is a part of SOLID^[About] which is a part of OOD and was introduced by Uncle Bob. It is about loose coupling between classes(layers...). Class should not be depended on concrete realization, class should be depended on abstraction/interface

Problem:

//A -> B
class A {
  B b

  func foo() {
     b = B();
  }
}

Solution:

//A -> IB <|- B
//client[A -> IB] <|- B is the Inversion 
class A {
  B ib

  func foo() {
     ib = B()
  }
}

Now A is not depended on B(one to one), now A is depended on interface IB which is implemented by B, it means that A depends on multiple realization of IB(one to many)

DIP + DI

[Dependency Injection(DI)]

• [Factory Method]
• Service Locator
• [IoC-container(framework)]

More complex example

Dependency rule in multi layer/module structure

Pseudocode:

interface InterfaceInputPort {
    func input()
}

interface InterfaceOutputPort {
    func output()
}

class A: InterfaceOutputPort {

    let inputPort = B(outputPort: self)

    func output() {
        print("output")
    }
}

class B: InterfaceInputPort {
    let outputPort: InterfaceOutputPort

    init(outputPort: InterfaceOutputPort) {
        self.outputPort = outputPort
    }

    func input() {
        print("input")
    }
}

[DIP vs DI vs IoC]