Our SOA tutorials are all in one place! These tutorials are valuable reference guides to help you learn more about the most important SOA techniques and technologies. In our tutorials you will find the definitions and explanations you need to get started as well the latest SOA news, trends, best practices, and tools you need to optimize your SOA implementation and strategy. The tutorials below are listed in alphabetical order, from Ajax to WSDL.
Use the links at the right to go directly to the tutorial you're looking for, or read about each tutorial in more detail from the annotated list below.
Ajax technologies have helped make Internet access one of the most, if not the most, important reasons for using a computer. Ajax has made RIAs, including video, music, and dynamic user interfaces--features once limited to desktop applications--more readily available on Web pages. As a result, use of such desktop apps has declined. At the same time, use of Web services has increased.
Read the Ajax tutorial.
Business Process Execution Language (BPEL), short for Web Services Business Process Execution Language (WS-BPEL), is an executable dialect of XML that allows for the modeling of interactions between Web services. Such modeling is valuable for successful business process management (BPM) and service-oriented architecture (SOA) implementation. BPEL was standardized by OASIS in 2004, after collaborative efforts to create the language by Microsoft, IBM, and other companies.
Read the BPEL tutorial.
Business Process Management (BPM) describes the methods and techniques used to make a business process more efficient, adaptive, and effective for accomplishing a specific task. With constantly changing technologies and market environments within the application development world, a business process can be proven insufficient shortly after it's implemented. Successful BPM requires that business processes be carefully modeled, regularly monitored, and frequently updated to optimize their performance.
Read the BPM tutorial.
In the early days of Web services, most of the attention centered on application integration and workflow. But data got lost in the shuffle. Now architects are finding themselves dealing with performance issues caused by an inability to access data and to move it around in the same agile way they are handling their application logic.
Read the data integration tutorial.
An enterprise mashup combines applications and/or data from disparate sources into a new service. They are most often created using Ajax techniques or with available mashup servers. By bringing together information and features once independent of one another, mashups have simplified many tasks. A common example is a mashup that combines apartment ads on Craigslist with Google maps, allowing a user to view the location of each advertised apartment without having to search for it himself.
Read the enterprise mashups tutorial.
The enterprise service bus (ESB) is a software infrastructure that facilitates application integration. An ESB is valuable to the implementation of a service-oriented architecture because it exchanges messages, executes transactions, orchestrates services, and performs publish and subscribe functions between disparate and distributed applications.
Read the ESB tutorial.
SOA governance is a broad concept, defined as the processes and strategies used to oversee the adoption, implementation, and performance of a service-oriented architecture (SOA). Commonly, SOA governance is divided between design governance and runtime governance. SOA governance can also be divided between the line-of-business and the IT department. Recent research shows that the business side is becoming more and more essential to SOA governance.
Read the SOA governance tutorial.
The work behind OSGi began in 1999, when embedded systems vendors and networking providers came together to create a set of standards for a Java-based service framework that could be remotely managed. But since then the effort has evolved well beyond its embedded system roots into a kind of universal interoperability layer and has shed its original name, Open Services Gateway initiative, leaving the acronym OSGi.
Read the OSGi mini tutorial.
Representational state transfer (REST) has made progress in various application development tooling platforms and its uses in SOA are increasing in number and importance. REST has now moved from a bleeding edge developmental style to one with widespread vendor and open source support. Whether you are a developer, architect, manager or executive, RESTful Web services are likely to become a common occurrence in your applications portfolio.
Read the REST tutorial.
Simple Object Access Protocol (SOAP) was created in 1998 by Dave Winer, Don Box, Bob Atkinson, and Mohsen Al-Ghosein with backing by Microsoft. SOAP is a messaging framework that gained widespread support in the Java, .NET and open source communities during the early part of the 2000s. It has served as the foundation of many Web services projects and provides the mechanism by which many other Web services standards communicate.
Read the SOAP tutorial.
The Web Services Description Language (WSDL) is an XML based language used to describe the services offered by a business and provides a way for other businesses to access those services electronically. Services listed in The Universal Description, Discovery, and Integration (UDDI) registry are described using WSDL. WSDL is frequently used with SOAP and XML schema to provide Web services over the Internet.
Read the WSDL tutorial.