What is service oriented architecture

Francisco Afonso October 22, 5 min read. Francisco Menezes August 21, 9 min read. Keith L. Murphy June 23, 7 min read. Be the first to know! Get amazing low-code content right in your inbox. You're one click away from awesome content. Yes, I'd like to receive OutSystems marketing communications. I can unsubscribe here.

Thank you for subscribing! See you soon Close By submitting this form you consent to the processing of your personal data by OutSystems as described in our Terms and our Privacy Statement. When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to.

The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.

More information. Allow All. Strictly Necessary Cookies Always Active. Performance Cookies Performance Cookies. Functional Cookies Functional Cookies. Targeting Cookies Targeting Cookies. Confirm My Choices. Clear Filters.

Information storage and access. Consent Leg. Select All Vendors. All Consent Allowed. Consent Purposes. Location Based Ads Consent Allowed. Legitimate Interest Purposes. Personalize Require Opt-Out. A service provider creates web services and provides them to a service registry. The service provider is responsible for the terms of use of the service. A service broker or service registry is responsible for providing information about the service to a requester.

A broker may be public or private. A service requester finds a service in a service broker or service registry and then will connect with the service provider to receive the service. The concept of services introduced by service-oriented architecture has become what is now a central component of modern cloud computing and virtualization in things like middleware and microservices.

Because of their similarities, SOA and microservices architecture are often confused. The main characteristic that can help differentiate between them is their scope: SOA is an enterprise-wide approach to architecture, while microservices is an implementation strategy within application development teams.

They also communicate to their respective components differently, with SOA using an ESB while microservices can communicate with each other statelessly, through language-agnostic APIs. The language-agnostic aspect of APIs in microservices also allows dev teams to choose what tools they want to work with.

In these ways, microservices can be more tolerant and flexible. SOA is also sometimes confused with Software-as-a-service. SaaS is a form of cloud computing that delivers a cloud application—and all its underlying IT infrastructure and platforms—to users. Users interact with the software through a web browser on their computer or mobile devices. Because of advancements in container technology, microservices have become the foundation for cloud-native applications—loosely-coupled microservices that are deployed in Linux containers and connected through APIs or a mesh network for message routing.

This means faster software development, automatic deployment, and regular updates without the limitations of monolithic development cycles. Sign up for our free newsletter, Red Hat Shares. Open hybrid cloud Support Developers Partners Start a trial. Enter your keywords. Featured links. It uses common communication standards to speed up and streamline the service integrations in applications. Each service in SOA is a complete business function in itself.

The services are published in such a way that it makes it easy for the developers to assemble their apps using those services. Note that SOA is different from microservice architecture. SOA allows users to combine a large number of facilities from existing services to form applications. SOA encompasses a set of design principles that structure system development and provide means for integrating components into a coherent and decentralized system. SOA-based computing packages functionalities into a set of interoperable services, which can be integrated into different software systems belonging to separate business domains.

There are two major roles within Service-oriented Architecture: Service provider: The service provider is the maintainer of the service and the organization that makes available one or more services for others to use.

To advertise services, the provider can publish them in a registry, together with a service contract that specifies the nature of the service, how to use it, the requirements for the service, and the fees charged. Service consumer: The service consumer can locate the service metadata in the registry and develop the required client components to bind and use the service.