Monolithic Architecture

In a monolithic architecture, an application is developed as a single, self-contained entity. A few examples of the many different components of the application that are all closely coupled and deployed as a single unit include the user interface, business logic, and data access layer. Monolithic architectures are typically easier to develop and test initially, as they have a simpler structure. Monolithic architectures can be difficult to scale as an application gets bigger and more sophisticated, though.

Advantages of Monolithic Architecture:

1. Simplicity: Monolithic architectures are relatively simple to develop and deploy initially.
2. Performance: Since there is no network overhead, inter-component communication in a monolithic design is typically quicker.
3. Development Efficiency: Debugging and testing are generally easier in a monolithic architecture since the entire application is in one codebase.

Considerations of Monolithic Architecture:

1. Scalability: Scaling a monolithic application can be challenging, as it requires scaling the entire application even if only certain components experience increased load.
2. Flexibility: Making changes to one component of a monolithic application can be risky since any change may impact the entire system.
3. Technology Stack: In a monolithic architecture, all components must use the same technology stack, limiting the ability to adopt new technologies.

There are various architecture patterns in design patterns but for creating and deploying applications, the most frequently used architecture patterns are listed below that we are going to discuss below that are as follows:

1. Monolithic Architecture 
2. Microservice Architecture
3. Serverless Architectures