When designing application architecture on IBM Cloud, which pattern is most beneficial for achieving scalability and manageability for a web application?

Question

Options

• AMonolithic architecture
• BMicroservices architecture
• CBig data architecture
• DServerless architecture

• A
  6% (3)
• B
  81% (42)
• C
  10% (5)
• D
  4% (2)

Explanation

Microservices architecture is the best choice for scalability and manageability because it decomposes an application into small, independent services that can be scaled, deployed, and updated individually - making it ideal for modern cloud-native web applications on IBM Cloud.

Why the others are wrong:

• A (Monolithic): All components are tightly coupled in a single deployable unit, making it hard to scale specific parts or manage independently as the app grows.
• C (Big data): This is a data processing pattern (think Hadoop/Spark pipelines), not a general web application architecture pattern.
• D (Serverless): While serverless offers scalability, it's optimized for event-driven, stateless functions - not holistic web application manageability at the architecture level; it also introduces cold starts and vendor lock-in concerns.

Memory tip: Think "Micro = Manageable" - microservices let teams own small pieces independently, which directly maps to both scalability (scale only what's needed) and manageability (each service has a clear boundary and owner).

No community discussion yet for this question.