登录查看更多内容

What distinguishes a service-oriented architecture from a microservices architecture?

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

Service-oriented architecture (SOA) and microservices architecture (MSA) are two popular approaches to designing and developing software applications that are composed of multiple components that communicate over a network. Both architectures aim to achieve modularity, scalability, reusability, and maintainability of the software systems. However, they also have some significant differences that affect how they are implemented and managed. In this article, you will learn what distinguishes a service-oriented architecture from a microservices architecture in terms of scope, granularity, communication, governance, and evolution.

此文章中的业界达人

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

Amandeep Nagpal ↗?

Dean I Data Analytics, Mentoring, Training | Tech Enthusiast | EdTech Futurist | Do-gooder I Minimalist
Siddhartha Sood

True Blue IBM'er | Executive Architect for Hybrid Cloud | Travel & Transportation Architecture Lead | IBM Master…

1 Scope of services

One of the main differences between SOA and MSA is the scope of the services that they define and expose. In SOA, services are usually coarse-grained and business-oriented, meaning that they encapsulate a high-level business function or process that can be reused by different consumers. For example, a service might implement a payment processing or an order fulfillment logic. In MSA, services are more fine-grained and domain-oriented, meaning that they focus on a specific subdomain or bounded context within the business domain. For example, a service might handle only the inventory management or the customer loyalty program.

添加您的观点

Siddhartha Sood

True Blue IBM'er | Executive Architect for Hybrid Cloud | Travel & Transportation Architecture Lead | IBM Master Inventor | IBM Academy of Technology Member | Mentor
举报内容
SOA architectural style focuses on breaking functionality into services that focus more on reusability Soa services can be fine grained or coarse grained (composite) hence can do multiple things such as orchestrating set of functions to achieve a larger process goal. Compared to monoliths that are centralised, soa helps move towards a hybrid approach where services ownership could be decentralised but the platform ownership is still centralised. Microservices is another evolution where the focus is building domain aligned capabilities with a well defined bounded context which are owned and managed by independent teams end to end.

已翻译

赞

2 Granularity of components

Another difference between SOA and MSA is the granularity of the components that make up the services. In SOA, components are often large and complex, containing multiple layers and dependencies within themselves. They may also share common libraries or frameworks with other components. In MSA, components are small and simple, following the principle of single responsibility. They have minimal dependencies and do not share code or data with other components. Each component can be deployed and updated independently, without affecting the rest of the system.

添加您的观点

Siddhartha Sood

True Blue IBM'er | Executive Architect for Hybrid Cloud | Travel & Transportation Architecture Lead | IBM Master Inventor | IBM Academy of Technology Member | Mentor
举报内容
The key is the ability to manage and deploy capabilities independent of each other and hence being able to evolve these capabilities independently.

已翻译

赞

3 Communication between services

A third difference between SOA and MSA is the communication between the services. In SOA, services typically communicate through a centralized broker or bus that mediates and orchestrates the interactions. The broker or bus may also provide additional features such as routing, transformation, security, or monitoring. The communication is often based on standardized protocols and formats, such as SOAP or XML. In MSA, services communicate directly with each other, without a central point of control or coordination. The communication is often based on lightweight protocols and formats, such as REST or JSON.

添加您的观点

Amandeep Nagpal ↗?

Dean I Data Analytics, Mentoring, Training | Tech Enthusiast | EdTech Futurist | Do-gooder I Minimalist
举报内容
In terms of Fault Isolation and Resilience, SOA systems may face more challenges in fault isolation, as issues in one service could potentially affect other services relying on it. In contrast, MSA, by design, promotes resilience through isolation. A failure in one microservice ideally should not cascade to other microservices, improving the overall system's fault tolerance. Regarding Scaling Strategy, SOA services might be scaled vertically by adding more resources to the existing service instances to handle increased load. Meanwhile, MSA favors horizontal scaling, where additional instances of a microservice are added to distribute the load. This aligns with the idea of scaling individual components based on their specific needs.

已翻译

赞
Siddhartha Sood

True Blue IBM'er | Executive Architect for Hybrid Cloud | Travel & Transportation Architecture Lead | IBM Master Inventor | IBM Academy of Technology Member | Mentor
举报内容
Communication typically depends on nature of interactions which could be synchronous or asynchronous both of which have evolved over a period of time between SOA and Microservices architectures. Asynchronous communications has evolved further with the advent of event driven architectures and the ability for Microservices to be able to react to events which is more closer to how businesses really work.

已翻译

赞

4 Governance of services

A fourth difference between SOA and MSA is the governance of the services. In SOA, services are governed by a top-down approach, where a central authority defines and enforces the policies, standards, and contracts for the services. The governance is often formal and rigid, requiring extensive documentation and compliance. In MSA, services are governed by a bottom-up approach, where each service team has the autonomy and responsibility to design and manage their own services. The governance is often informal and flexible, relying on conventions and collaboration.

添加您的观点

5 Evolution of services

A fifth difference between SOA and MSA is the evolution of the services. In SOA, services are designed to be stable and backward-compatible, meaning that they do not change frequently or break the existing contracts with the consumers. The evolution is often slow and cautious, requiring careful planning and coordination. In MSA, services are designed to be adaptable and forward-compatible, meaning that they can change rapidly or introduce new features without affecting the consumers. The evolution is often fast and agile, enabling continuous delivery and experimentation.

添加您的观点

6 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?

添加您的观点

Siddhartha Sood

True Blue IBM'er | Executive Architect for Hybrid Cloud | Travel & Transportation Architecture Lead | IBM Master Inventor | IBM Academy of Technology Member | Mentor
举报内容
The biggest difference according to me is centralisation v/s decentralisation. Microservices promotes decentralisation and autonomy for full stack product teams to that the service capability can independently evolve. This helps better business alignment and ability for teams to quickly react to business needs.

已翻译

赞

Computer Science

+ 关注

给文章评分

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

很棒不太好

举报此文章

查看全部

What distinguishes a service-oriented architecture from a microservices architecture?

1

2

3

4

5

6

1 Scope of services

2 Granularity of components

3 Communication between services

4 Governance of services

5 Evolution of services

6 Here’s what else to consider

Computer Science

给文章评分

感谢您的反馈

更多Computer Science相关文章

更多相关阅读内容

What distinguishes a service-oriented architecture from a microservices architecture?

1

2

3

4

5

6

1 Scope of services

2 Granularity of components

3 Communication between services

4 Governance of services

5 Evolution of services

6 Here’s what else to consider

Computer Science

给文章评分

感谢您的反馈

查看其他技能