How is service-oriented architecture different from other system architecture patterns?

由人工智能和领英社区提供技术支持

Service-oriented architecture (SOA) is a popular and widely used system architecture pattern that aims to provide reusable, interoperable, and loosely coupled services that can communicate with each other through standardized protocols and interfaces. SOA has many benefits, such as flexibility, scalability, maintainability, and agility, but it also differs from other system architecture patterns in several ways. In this article, you will learn how SOA compares to some of the most common system architecture patterns and styles, such as monolithic, layered, microservices, and event-driven architectures.

此文章中的业界达人

由社区从 3 条内容中精选。了解更多

Kamal Ponaka

Director & Distinguished Engineer

1 Monolithic architecture

A monolithic architecture is a system architecture pattern that consists of a single, self-contained, and tightly coupled application that handles all the business logic, data access, user interface, and communication functions. Monolithic architectures are easy to develop, test, and deploy, but they also have many drawbacks, such as low modularity, high complexity, poor scalability, and difficult maintenance. SOA differs from monolithic architecture by breaking down the system into smaller, independent, and loosely coupled services that can be developed, tested, and deployed separately, and that can interact with each other through well-defined interfaces and protocols.

添加您的观点

Kamal Ponaka

Director & Distinguished Engineer
举报内容
Monolithic architecture also complicates the deployment process and require the extended hours of deployment window which impacts the uptime. We can't achieve the 99.9% uptime with complex monolithic architecture. In contrast, Service Oriented Architecture allows us to break down the services, scale the services according to the user traffic and load. It also allows to deploy the services independently which allows us the parallel deployment reducing the downtime/deployment window

已翻译

赞

2 Layered architecture

A layered architecture is a system architecture pattern that organizes the system into a hierarchy of layers, each of which has a specific responsibility and interacts only with the adjacent layers. For example, a typical layered architecture may have four layers: presentation, business, data access, and data. Layered architectures are easy to understand, modular, and reusable, but they also have some limitations, such as low performance, high coupling, and rigid structure. SOA differs from layered architecture by allowing the services to communicate with any other service in the system, regardless of the layer they belong to, and by enabling more flexibility and dynamism in the system design.

添加您的观点

3 Microservices architecture

A microservices architecture is a system architecture pattern that is similar to SOA, but with a finer granularity and a stronger focus on domain-driven design. A microservices architecture consists of a collection of small, autonomous, and self-contained services that are aligned with the business domains and that communicate with each other through lightweight protocols and messages. Microservices architectures are highly scalable, resilient, and adaptable, but they also introduce more complexity, overhead, and challenges in terms of testing, monitoring, and coordination. SOA differs from microservices architecture by having a broader scope and a more heterogeneous nature, as SOA services can vary in size, technology, and functionality, and can span across multiple domains and organizations.

添加您的观点

Kamal Ponaka

Director & Distinguished Engineer
举报内容
As we are moving towards Cloud Native and Container based platforms, Service Oriented Architecture deployment won't suit for newer platforms. Microservice architecture follows 12 Factor principles and one of the biggest advantage is auto scaling. There is also downside of microservice architecture where an operation/method in Service Oriented Architecture will become a microservice resulting too many microservices introducing hefty operation burden and maintenance. we need to strike the balance between the number of microservices and often Service Mesh and Proxy are great adds.

已翻译

赞

4 Event-driven architecture

An event-driven architecture is a system architecture pattern that is based on the production, detection, consumption, and reaction of events that occur in the system. An event is a significant change in the state or condition of the system or its components, such as a user action, a sensor reading, or a message arrival. An event-driven architecture consists of event producers, event consumers, and event brokers that facilitate the asynchronous and decoupled communication between the system elements. Event-driven architectures are responsive, scalable, and adaptable, but they also require careful design, governance, and testing to ensure reliability, consistency, and security. SOA differs from event-driven architecture by not relying solely on events as the means of communication, but also on other types of protocols and interfaces, such as SOAP, REST, or RPC, that can provide more synchronous and direct interactions between the services.

添加您的观点

Kamal Ponaka

Director & Distinguished Engineer
举报内容
Even-driven architecture is generally considered for asynchronous communication with the use of technologies like Message Queues. This architecture doesn't suit for real-time user transactions and generally used in backend systems

已翻译

赞

5 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Systems Management

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

How is service-oriented architecture different from other system architecture patterns?

1

2

3

4

5

1 Monolithic architecture

2 Layered architecture

3 Microservices architecture

4 Event-driven architecture

5 Here’s what else to consider

Systems Management

给文章评分

感谢您的反馈

更多Systems Management相关文章

更多相关阅读内容