brainfck.org
Topics Books Journal Tags
Information hiding

  • Introduced by David Parnas in “Information Distribution Aspects of Design Methodology”
  • hide as many details as possible behind a module / microservice boundary
  • Parnas identified following benefits:
    • improved development time
    • comprehensibility
      • each module is isolated and therefore better to understand
    • flexibility

Links to this note

  • Building Microservices (2nd edition)
    • Microservices embrace the concept of Information hiding
        -   bounded contexts hide implementation details ([Information hiding](/t/information-hiding/))
back to top

prev post next post



Powered by Hugo, based on the Er theme. 2009-2023 Victor Dorneanu - All rights reserved