Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Architecture
Architectureeasy

Coupling vs cohesion — what do you want and why?

Tags
#coupling#cohesion#design
Back to categoryPractice quiz

Answer

You want low coupling (modules depend on each other as little as possible) and high cohesion (a module’s code belongs together). That makes changes safer: fewer ripple effects and clearer responsibilities.

Related questions

Microservices
Why is sharing one database between microservices risky?
#shared-database#coupling#data-ownership
Monoliths
What is a “big ball of mud” and how can you recognize it?
#maintainability#coupling#code-smell
Monoliths
What is a “distributed monolith” and how do you avoid it?
#distributed-monolith#coupling#microservices
Java
Interface vs Abstract Class?
#oop#interface#abstract-class