Delete empty folders

Author: everysoftware

README.md

@@ -114,42 +114,3 @@ repository contains a collection of design patterns, principles, and best practi
 | 9  | [Identity Map]()         | Ensure that each object gets loaded only once by keeping every loaded object in a map. Looks up objects using the map when referring to them                                    |
 | 10 | [Unit of Work]()         | Maintain a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems                             |
 | 11 | [Data Transfer Object]() | An object that carries data between processes. The data transfer object is not tied to any specific operation and does not have any behavior                                    |
-
-## Architectural Approaches
-
-| #  | Pattern                       | Description                                                                                                                   |
-|----|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
-| 1  | [Monolithic Architecture]()   | A single-tiered software application in which different components combined into a single program running as a single process |
-| 2  | [Microservices]()             | Architectural style that structures an application as a collection of small autonomous services                               |
-| 3  | [Serverless]()                | Architectural style that allows you to build and run applications and services without having to manage infrastructure        |
-| 4  | [Event-Driven]()              | Architectural style that produces, detects, consumes, and reacts to events in a system                                        |
-| 5  | [Service-Oriented]()          | Architectural style that structures an application as a collection of loosely coupled services                                |
-| 6  | [MVC]()                       | Architectural pattern that separates an application into three main components: Model, View, and Controller                   |
-| 7  | [Onion]()                     | Architectural pattern that layers an application by wrapping it with layers of abstraction                                    |
-| 8  | [Hexagonal]()                 | Architectural pattern that structures an application around its core business logic                                           |
-| 9  | [Clean Architecture]()        | Architectural pattern that separates concerns into layers, with dependencies pointing towards the center                      |
-| 10 | [CQRS]()                      | Architectural pattern that separates read and write operations for a data store                                               |
-| 11 | [Event Sourcing]()            | Architectural pattern that logs all changes to an application's state as a sequence of events                                 |
-| 12 | [Domain-Driven Design]()      | Architectural pattern that focuses on the core domain and domain logic                                                        |
-| 13 | [Event-driven architecture]() | A pattern that produces, detects, consumes, and reacts to events in a system                                                  |
-
-## Microservices Patterns
-
-| #  | Pattern                      | Description                                                                                               |
-|----|------------------------------|-----------------------------------------------------------------------------------------------------------|
-| 1  | [Reverse Proxy]()            | Act as an intermediary for requests from clients seeking resources from servers                           |
-| 2  | [Load Balancer]()            | Distribute incoming network traffic across multiple servers to ensure that no single server is overworked |
-| 3  | [API Gateway]()              | Aggregate multiple services into a single API                                                             |
-| 4  | [Broker]()                   | Act as an intermediary for messages between two applications                                              |
-| 5  | [SAGA]()                     | A sequence of local transactions where each transaction updates data within a single service              |
-| 6  | [2PC]()                      | A distributed transaction that ensures all-or-nothing semantics for a transaction                         |
-| 7  | [Transactional Outbox]()     | A pattern that ensures exactly-once delivery of messages                                                  |
-| 8  | [Compensating Transaction]() | A pattern that undoes the work of a failed transaction                                                    |
-| 9  | [Sharding]()                 | Partition a database into smaller, faster, and more easily managed parts                                  |
-| 10 | [Service Discovery]()        | Automatically locate services in a distributed system                                                     |
-| 11 | [Health Check]()             | Monitor the health of a service or a system                                                               |
-| 12 | [Circuit Breaker]()          | Detect failures and encapsulate the logic of preventing a failure from constantly recurring               |
-| 13 | [Leader Election]()          | Choose a leader from a group of distributed nodes                                                         |
-| 14 | [Sidecar]()                  | Extend a service's functionality without changing the service itself                                      |
-| 15 | [Bulkhead]()                 | Isolate elements of an application into pools so that if one fails, the others will continue to function  |
-| 16 | [Back Pressure]()            | Control the rate of data transfer between two systems                                                     |