Garofolo's definition: a monolith is not a deployment strategy or a single repository — it is a data model in which multiple unrelated domains (authentication, feature tracking, etc.) share one representation (e.g. one users table keyed by user ID). Extracting that same model into separate servers over HTTP produces a 'distributed monolith': access patterns stay identical but method calls become HTTP calls with more failure modes and operational concerns.