architectural boundary. It separates the abstract from the concrete. All source code dependencies cross that curved line pointing in the same direction, toward the abstract side.
- Chapter 11 DIP: The Dependency Inversion Principle
- from Clean Architecture: A Craftsman's Guide to Software Structure and Design, First Edition
- Publisher: Prentice Hall
- Released: September 2017
interface to implementation separation. api vs service
Share this highlighthttp://www.safaribooksonline.com/a/clean-architecture-a/17911148/