volume_mute

Architecture for a Music Distribution System

publish date: 2026/06/11 07:14:53.647742 UTC

volume_mute

An online music distribution system (similar to iTunes) needs to sell and distribute music over the Internet. It must handle a large catalogue of music, manage user accounts and purchases, stream or download audio files, and process payments. Which combination of architectural patterns forms the most appropriate base architecture, and why?

Layered architecture only, with all functionality in a single monolithic stack

Pipe and Filter only - because music files are processed sequentially like a pipeline

Repository only - because all data is stored centrally and no client interaction is needed

Client-Server as the primary pattern (clients access music, payment, and streaming services from separate servers) combined with a Repository (for the central music catalogue and user account database) and MVC for the web front-end managing catalogue browsing and user interaction

Correct Answer

Explanation

A music distribution system naturally uses multiple patterns: Client-Server is the primary pattern because users (clients) access distinct services - catalogue browsing, streaming/download, and payment processing - from separate servers. A Repository pattern manages the large shared music catalogue and user account database. MVC suits the web front-end where the same catalogue data is presented in different views (search results, recommendations, album pages) and user interactions are separated from the data model.

Reference

Software Engineering, Ian Sommerville, 10th edition

Quizzes you can take where this question appears

Architecture Design: Exercises