Bird
0
0

Consider a system where all modules directly access a single shared database without any abstraction layer. What is the main anti-pattern here?

medium📝 Conceptual Q13 of 15
LLD - Advanced LLD Concepts
Consider a system where all modules directly access a single shared database without any abstraction layer. What is the main anti-pattern here?
ATight Coupling
BGod Object
CSpaghetti Architecture
DEvent-Driven Design
Step-by-Step Solution
Solution:

  1. Step 1: Analyze direct database access and identify the anti-pattern

    When modules directly access the database without abstraction, they become tightly coupled to the database schema. Tight Coupling means components depend heavily on each other, reducing flexibility and increasing maintenance difficulty.

  2. Final Answer:

    Tight Coupling -> Option A

  3. Quick Check:

    Direct DB access = Tight Coupling [OK]
Quick Trick: Direct DB access causes tight coupling [OK]
Common Mistakes:
  • Confusing tight coupling with God Object
  • Thinking event-driven design fits here
  • Mixing spaghetti architecture with tight coupling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More LLD Quizzes
Advanced LLD Concepts - Domain-Driven Design basics - Quiz 4medium Design — Chess Game - Why chess tests polymorphism and strategy - Quiz 1easy Design — Food Delivery System - Delivery agent assignment - Quiz 2easy Design — Hotel Booking System - Cancellation and refund policy - Quiz 11easy Design — Hotel Booking System - Availability checking - Quiz 12easy Design — Hotel Booking System - Hotel, Room, Booking classes - Quiz 6medium Design — Online Shopping Cart - Order state machine - Quiz 5medium Design — Splitwise (Expense Sharing) - User, Group, Expense classes - Quiz 1easy Design — Splitwise (Expense Sharing) - User, Group, Expense classes - Quiz 4medium Design — Splitwise (Expense Sharing) - Balance calculation algorithm - Quiz 12easy