Architecture Styles

The difference between a Styles and Patterns.

• A Style shows how we organize code and systems.
• A Pattern shows how a problem can be solved.

In a simple example of Object Oriented programming (OO)

• A developer might ...

Style

Organize their code in a clean architecture style, MVVC, MVC for better readability, organization and blueprint for everyone to understand how the code is organized.

Pattern

Solve a problem of a need to only use a single instance of an object throughout the app lifetime so they would use a singleton pattern that restricts the instantion to only a single instance.

There is a debate if they are same or not but you can see if we apply this logic, they are not the same.

Big-Compute

---

Uses large scale workloads that require high number of CPU cores to run discrete tasks in parallel or grouped together in tightly coupled tasks.

Big-Data

---

Handles ingestion (egress), processings and analysis of large or complex data structures using batch and realtime streams.

Event-Driven

---

Enables publishers to broadcast events and consumers listen for those events in near real-time that keeps them decoupled.

Microservices

---

Small independent and loosely coupled processes that are highly scalable while communicating through APIs.

N-Tier

---

Seperates the application into multiple layers based on responsibility. The most common is the 3-tier which includes the presentation, the application, and data storage layer.

Web-queue-worker

---

Uses a queue to process resource intesive or batch jobs through a web front-end client such as a browser.