🪴 Quartz 4.0

Separation of Concerns

2 min read

Arch

Good architecture allows you to defer decisions to later.
A good architect maximizes the number of decisions not made.
  1. N-Layered Architecture
  2. Domain Driven Design
  3. Hexagonal ( Ports and Adapters )
  4. Onion Arch.
  5. Clean Arch.
  6. BCE
  7. DCI

Framerworks

  • Never implement on a class from framework, which make our code couple with the framework.
  • Create a interface and use it like a plugin instead.
  • DI is need to abstracted to entry level layer, we might need to avoid explicit DI of framerworks in our business layer.

MVC

  • Is a delivery pattern.
  • The business application doesn’t know anything about the MVC

Cross Cutting Concerns

  • Treating CCC
    • Infrastructure.
    • Domain
    • Decorators (Wrappers)

ORM Can i use ORM ?

Use Case Layer (Business layer) (Interactor)

  • Are application specific business rules.
  • Which on instansiation accepts a gateway (of its boundary type) to work.
    • Boundaries(interfaces) are defined by(for) use case layer..
    • The gateway(impl of boundary) is expected to implement by(for) the data layer.
    • Which makes swap of data layer easy, thus achieves loose coupling.
  • Where do we put these second, lower level business rules? In the Entity object. The Interactor tells the Entity what to do.

Boundaries

  • Boundaries are interfaces.
  • Being defined by Business layers.

Entities

  • Application independent business rules.
  • There may be many entities involve in a particular use case(user event)

DAO - Repositories (Adapters)

  • It lies on the outer most layer.
  • Which acts as a plugin to the use case layer.
  1. Web is an IO channel, and there is no need for our soruce architecture to show as for WEB.
  2. Service layer is need to be use case driven.

References

  1. Evolution of arch
  2. Clean Arch By Martin YT
  3. Clean Arch By Martin - Blog
  4. Clean Arch Impl in Java
  5. Clean Arch about databases
  6. Entity(Domain) can be shared across layers ?
  7. BCE
  8. Pack by features, not layers
  9. Cross Cutting Concerns

Graph View