What types of architecture have you encountered in your work?

In my work, I have encountered the following types of architecture:

• Monolithic Architecture: A traditional approach where all components of the application are tightly coupled and deployed as a single unit. Simple to develop in the initial stages, but complex to scale and modify.
• Multi-tier (N-Tier) Architecture: Dividing the application into logical layers (Presentation, Business Logic, Data Access). Provides better modularity and manageability compared to monolith.
• Microservices Architecture: The application is broken down into small, independent services, each performing a specific business function. Services interact over the network. High scalability, flexibility, and resilience, but requires more complex infrastructure and management.
• SOA (Service-Oriented Architecture): An architecture built around business services that are accessible via standardized protocols. Aimed at reusing functionality.
• Layered Architecture: Usually involves dividing into Presentation, Application, Domain, and Infrastructure layers. Emphasizes separating business logic (Domain) from technical details (Infrastructure).
• Hexagonal Architecture (Ports and Adapters): Focuses on isolating core business logic from external dependencies (databases, UI, external services) through ports and adapters. Enhances testability and flexibility.
• Event-Driven Architecture (EDA): Components interact by publishing and subscribing to events. Well-suited for systems with asynchronous processes and high degrees of parallelism.

Most often, I worked with multi-tier and monolithic architectures in early-stage projects, and also participated in refactoring monoliths towards multi-tier and, to a lesser extent, microservices architectures. I applied principles of layered and hexagonal architecture when designing individual modules within larger systems.