We are independent & ad-supported. We may earn a commission for purchases made through our links.

Advertiser Disclosure

Our website is an independent, advertising-supported platform. We provide our content free of charge to our readers, and to keep it that way, we rely on revenue generated through advertisements and affiliate partnerships. This means that when you click on certain links on our site and make a purchase, we may earn a commission. Learn more.

How We Make Money

We sustain our operations through affiliate commissions and advertising. If you click on an affiliate link and make a purchase, we may receive a commission from the merchant at no additional cost to you. We also display advertisements on our website, which help generate revenue to support our work and keep our content free for readers. Our editorial team operates independently from our advertising and affiliate partnerships to ensure that our content remains unbiased and focused on providing you with the best information and recommendations based on thorough research and honest evaluations. To remain transparent, we’ve provided a list of our current affiliate partners here.

What is Service Oriented Architectures?

By David White
Updated May 16, 2024
Our promise to you
EasyTechJunkie is dedicated to creating trustworthy, high-quality content that always prioritizes transparency, integrity, and inclusivity above all else. Our ensure that our content creation and review process includes rigorous fact-checking, evidence-based, and continual updates to ensure accuracy and reliability.

Our Promise to you

Founded in 2002, our company has been a trusted resource for readers seeking informative and engaging content. Our dedication to quality remains unwavering—and will never change. We follow a strict editorial policy, ensuring that our content is authored by highly qualified professionals and edited by subject matter experts. This guarantees that everything we publish is objective, accurate, and trustworthy.

Over the years, we've refined our approach to cover a wide range of topics, providing readers with reliable and practical advice to enhance their knowledge and skills. That's why millions of readers turn to us each year. Join us in celebrating the joy of learning, guided by standards you can trust.

Editorial Standards

At EasyTechJunkie, we are committed to creating content that you can trust. Our editorial process is designed to ensure that every piece of content we publish is accurate, reliable, and informative.

Our team of experienced writers and editors follows a strict set of guidelines to ensure the highest quality content. We conduct thorough research, fact-check all information, and rely on credible sources to back up our claims. Our content is reviewed by subject matter experts to ensure accuracy and clarity.

We believe in transparency and maintain editorial independence from our advertisers. Our team does not receive direct compensation from advertisers, allowing us to create unbiased content that prioritizes your interests.

Service Oriented Architectures are not exactly a new concept, but the ways they are used most often these days take advantage of new technology. At their most basic, Service Oriented Architectures describe the structure of software applications and interaction with a business model. The key word in all of this is Service.

A Service, as described in Service Oriented Architectures, is a specific software function that is independent of any other functions. For example, a bank's software protocols will necessarily include a Get Customer Balance request, whereby at the request of either the bank or the customer, a current balance is displayed. Get Customer Balance is a Service. Using the bank model, other Services include Process Deposit, Process Withdrawal, and so on.

Using Service Oriented Architectures, each of these Services works its way through the overall software system independently, while also using the same software systems. This sounds counter-intuitive, but it really isn't. Basically, various Services are using the same system to do the same thing for different results. Get Customer Balance for John Smith is the same function as Get Customer Balance for Jane Doe Enterprises, but the data involved are different. The beauty of Service Oriented Architectures is that the software is designed to process all Get Customer Balance commands in the same way, regardless of whether the customer is an individual like John Smith or a business like Jane Doe Enterprises.

A key to the success of Service Oriented Architectures is that the Services themselves are loosely coupled. That is, they are adaptable to differing circumstances. Should the Service command Get Customer Balance suddenly become Get Customer Balance for All Accounts, the software need not reinvent the virtual wheel; rather, the related Service can use the same basic protocols to achieve the same ends by slightly different means.

One way that Service Oriented Architectures are presented these days is via XML. This, for lack of a better term, generic programming language presents itself as a sort of lingua franca. All you need is a Web browser to be able to process XML requests. You don't need to be running the latest version of Windows or Mac OS. Logging in to the system and performing the necessary Services are taken care of because the computer doing the requesting and the computer providing the Service speak the same basic language.

EasyTechJunkie is dedicated to providing accurate and trustworthy information. We carefully select reputable sources and employ a rigorous fact-checking process to maintain the highest standards. To learn more about our commitment to accuracy, read our editorial process.

Discussion Comments

EasyTechJunkie, in your inbox

Our latest articles, guides, and more, delivered daily.

EasyTechJunkie, in your inbox

Our latest articles, guides, and more, delivered daily.