If a business has a short release cycle and high scalability requirements, and service interruption is not allowed during upgrades and expansions, which architecture is recommended for deploying…

Question

Options

• AMonolithic architecture
• BMicroservice Architecture
• CSOA architecture
• DVertical Architecture

• A
  17% (5)
• B
  72% (21)
• C
  3% (1)
• D
  7% (2)

Explanation

Microservice Architecture (B) is the right fit because it decomposes an application into small, independently deployable services - each service can be updated, scaled, or replaced without taking down the entire system, directly satisfying the zero-downtime and high-scalability requirements.

Why the others fail:

• A (Monolithic): A single deployable unit means any upgrade requires redeploying the whole app, causing interruptions and making granular scaling impossible.
• C (SOA): Service-Oriented Architecture shares some similarities with microservices but relies on heavyweight protocols (like SOAP/ESB) and coarser-grained services - it's harder to deploy individual pieces independently and doesn't scale as cleanly.
• D (Vertical Architecture): Scaling vertically (adding more power to one machine) hits hardware limits fast and still requires downtime for upgrades; it's not a deployment architecture in the same sense.

Memory tip: Think of microservices like a food court - each vendor (service) operates independently, can be swapped out or expanded without shutting down the whole mall, and a line at one stall doesn't block the others. If any part of the question mentions independent deployment, zero downtime, or fine-grained scaling, microservices is almost always the answer.

No community discussion yet for this question.