Distributed Systems - Chapter 02: Architectures

Flashcards covering key concepts and definitions from the lecture on architectures in distributed systems.

Architecture

A style formulated in terms of components with well-defined interfaces and how these components are configured into a system.

Connector

A mechanism that mediates communication, coordination, or cooperation among components.

Layered Architecture

An architectural style that organizes different layers for handling various aspects of application functionality and interaction.

Request/Response

A communication pattern where a client sends a request to a server and waits for a response.

Application Layering

An architectural framework consisting of interface, processing, and data layers to separate concerns within an application.

Service-oriented architecture (SOA)

An architectural style that enables services to communicate over a network with well-defined interfaces.

RESTful Architecture

An architectural style for designing networked applications using a stateless communication protocol, often HTTP.

Publish-Subscribe Architecture

A messaging pattern where senders (publishers) broadcast messages, and receivers (subscribers) subscribe to messages of interest.

Middleware

Software that acts as a bridge between different applications or services, facilitating communication and data management.

Multi-tiered Architecture

An architectural model that separates layers of an application into independent tiers, allowing for scalable and manageable designs.

Blockchain

A distributed ledger technology where transactions are recorded in a secure and immutable manner across multiple nodes.

Peer-to-Peer (P2P) Architecture

An architectural model where each participant (node) acts as both a client and a server in a decentralized manner.

Edge Computing

A distributed computing model that brings computation and data storage closer to the location where it is needed, improving response times and saving bandwidth.

Architecture is a style formulated in terms of components with well-defined and how these components are configured into a system.

interfaces.

A is a mechanism that mediates communication, coordination, or cooperation among components.

Connector.

Architecture organizes different layers for handling various aspects of application functionality and interaction.

Layered.

The /Response communication pattern involves a client sending a request to a server and waiting for a response.

Request.

Application consists of interface, processing, and data layers to separate concerns within an application.

Layering.

Service-oriented architecture (SOA) enables services to communicate over a network with well-defined _.

interfaces.

Architecture uses a stateless communication protocol, often HTTP, to design networked applications.

RESTful.

In a - architecture, senders (publishers) broadcast messages, and receivers (subscribers) subscribe to messages of interest.

Publish-Subscribe.

is software that acts as a bridge between different applications or services, facilitating communication and data management.

Middleware.

Multi-tiered Architecture separates layers of an application into independent , allowing for scalable and manageable designs.

tiers

What is Layered Architecture?

Layered Architecture is an architectural style that organizes different layers for handling various aspects of application functionality and interaction.

What are the layers involved in Layered Architecture?

The layers typically include presentation layer, application layer, business logic layer, and data access layer.

What is the purpose of Layered Architecture?

The purpose is to separate concerns within an application, making it easier to manage and scale.

How does Layered Architecture enhance maintainability?

It enhances maintainability by allowing changes in one layer without affecting others, thereby reducing interdependencies.

What is a common application of Layered Architecture?

Layered Architecture is commonly used in web applications, where the user interface, business logic, and database operations are separated into distinct layers.