A monolithic architecture is characterized by its single, unified codebase where all components are tightly coupled and run as a single process. This tight integration means that a failure in one part of the application, such as an unhandled exception or a memory leak in a specific module, can consume all available resources and lead to the failure of the entire application. This creates a single point of failure, which is a significant drawback of this design pattern and a primary driver for the adoption of alternative architectures like microservices.

A. This describes a microservices architecture, where loosely coupled, independent services constitute the application.
B. This is a benefit of microservices; in a monolith, any change requires redeploying the entire application.
D. Components in a monolith are typically built on a single technology stack and are not inherently platform-agnostic.

1. Cisco DevNet - Microservices Architecture: In the section "What is a monolithic architecture?"

the documentation states

"In a monolithic architecture

if a single function or component fails

the entire application may fail. This is often referred to as being 'tightly coupled'." This directly supports the correct answer.

Source: Cisco DevNet

"Microservices Architecture

" Introduction section.

2. Red Hat - What is a monolithic architecture?: This official vendor documentation explains the disadvantages of monoliths

stating

"If one component of the system fails

the entire system has to be stopped... This is known as being 'tightly coupled'."

Source: Red Hat Official Website

"What is a monolithic architecture?"

Disadvantages of monolithic architecture section.

3. Nadjarevic

I.

et al. (2017). Microservices in Practice. O'Reilly Media. While a book

its principles are foundational and align with vendor documentation. Chapter 1

"Monoliths and Microservices

" discusses that in a monolith

"a bug in any module (e.g.

memory leak) can bring down the entire process. A single unstable component can make the entire system unavailable."

Source: This is a widely cited text in software engineering

often used in university curricula. The principle is a standard definition.

4. Fowler

M. (2014). Microservices. Martin Fowler's seminal article

widely referenced in academic and professional contexts

notes a key disadvantage of monolithic systems: "a failure in any single part of the monolith risks bringing down the entire application."

Source: martinfowler.com

"Microservices

" Section: "Monolith First." This resource is considered authoritative in software architecture

equivalent to peer-reviewed material in its impact and rigor.