Bird
Raised Fist0

A startup built a monolithic system with many hardcoded values and a God Object managing most logic. They want to scale and maintain it easily. What is the best approach to fix these anti-patterns?

hard๐Ÿง  Conceptual Q15 of Q15
LLD - Advanced LLD Concepts
A startup built a monolithic system with many hardcoded values and a God Object managing most logic. They want to scale and maintain it easily. What is the best approach to fix these anti-patterns?
AIgnore scalability and focus only on adding new features.
BKeep the monolith but add more hardcoded values for speed.
CMerge all logic into one bigger God Object for simplicity.
DRefactor into microservices, externalize configuration, and split responsibilities into smaller components.
Step-by-Step Solution
Solution:
  1. Step 1: Identify problems in current system and choose best solution to fix anti-patterns

    Monolith with hardcoded values and God Object causes poor scalability and maintainability. Refactoring into microservices splits responsibilities, externalizing config removes hardcoding, improving scalability and maintainability.
  2. Final Answer:

    Refactor into microservices, externalize configuration, and split responsibilities into smaller components. -> Option D
  3. Quick Check:

    Microservices + external config fix anti-patterns [OK]
Quick Trick: Split monolith, externalize config, avoid God Object [OK]
Common Mistakes:
MISTAKES
  • Thinking bigger God Object improves simplicity
  • Adding more hardcoding for speed
  • Ignoring scalability needs

Want More Practice?

15+ quiz questions ยท All difficulty levels ยท Free

Free Signup - Practice All Questions
More LLD Quizzes