Architecture Styles and Patterns

 

1. Data-Centered Architecture

What It Is: Data-Centered Architecture is like a big library where all the important data is stored in one place. Different programs or parts of a system come to this central library to read or update information.

In Simple Terms: Imagine a big, shared notebook where everyone writes down their notes. Whenever someone needs information, they check this notebook. This way, everyone stays in sync and has access to the same information.

2. Data Flow Architecture

What It Is: Data Flow Architecture is like a factory assembly line where data moves through different stages. Each stage processes the data in some way, and then it moves on to the next stage.

In Simple Terms: Think of it like a conveyor belt in a factory. You put raw materials on one end, and as they move along the belt, different machines (stages) transform the materials until you have a finished product at the end.

3. Call and Return Architecture

What It Is: Call and Return Architecture is a style where one part of a system (a caller) makes a request or "call" to another part (a callee) to do something. After the callee completes the task, it "returns" the result back to the caller.

In Simple Terms: Imagine you’re asking a friend for help with a math problem. You call them, they work on the problem, and then they return with the answer. The call and return pattern is like this back-and-forth process between different parts of a system.

4. Object-Oriented Architecture

What It Is: Object-Oriented Architecture is like organizing everything in a system into neat boxes (called objects). Each box contains both data and functions that work with that data. These boxes can interact with each other to perform tasks.

In Simple Terms: Think of it like a collection of toy boxes. Each box represents a different type of toy (like cars, dolls, or action figures) and includes all the accessories and instructions for playing with those toys. You can play with or modify each box on its own, but they can also interact with each other in a game.

5. Layered Architecture

What It Is: Layered Architecture is like a multi-layered cake, where each layer has a specific role. For example, the bottom layer might handle the base ingredients, the middle layer adds flavor, and the top layer provides decoration. Each layer works independently but relies on the layer beneath it.

In Simple Terms: Imagine building a house. You start with the foundation (bottom layer), then add the walls (middle layer), and finally put on the roof (top layer). Each part has its job and depends on the parts below it to keep everything stable.