Service-Oriented Architecture

Start Date: 07/05/2020

Course Type: Common Course

Course Link:

Explore 1600+ online courses from top universities. Join Coursera today to learn data science, programming, business strategy, and more.

About Course

Based on an understanding of architectural styles, you will review architectures for web applications, then explore the basics of Service-Oriented Architecture (SOA) in two approaches: Web Services (WS*) and Representational State Transfer (REST) architecture. In the Capstone Project you will connect a Java-based Android application with Elasticsearch, a web service with a REST application programmer interface (API). After completing this course, you will be able to: • Describe SOA (Service-Oriented Architecture) to structure web-based systems. • Explain WS* services (i.e., SOAP over HTTP, WSDL, UDDI, BPEL). • Apply REST architecture (i.e., JSON over HTTP, URI). • Identify REST design principles. • Create a system using REST interfaces. • Apply microservice architecture.

Course Syllabus

In this module, we will introduce you to service-oriented architectures and their basic principles. Then, you will get a crash course on the technologies that underpin the Web, so that you are ready to learn about web services in the next module. This module also covers some earlier precursors of service-oriented architecture.

Deep Learning Specialization on Coursera

Course Introduction

Service-Oriented Architecture In this course you will learn the fundamental principles and techniques for designing and operating mobile devices in an open and affordable way. We will cover topics such as system design, architecture, platform, mobile communication, network operations and the management of mobile devices and their embedded systems. You will also learn to identify and translate good practices into flexible and attractive design solutions. The course will also focus on the use of open source design practices within the framework of a software development lifecycle. You’ll also learn the basics of the Mobile Device Management system in Mobile OSGi and how to use the built-in device management application. You’ll also learn about the design of the embedded systems that are driving the mobile devices to perform their tasks. This is where the course “service-oriented” comes in handy. Service-Oriented Architecture is the application of the open and low-cost approach to software development and deployment, and is the basis for many of the key architectural choices mobile devices make to facilitate their tasks. In this course, you will learn about the fundamental principles of service-oriented design and how to apply this approach to the design of mobile devices. You’ll also learn the basics of the mobile device management system in Mobile OSGi.Service-Oriented Architecture Mobile Device Operations Mobile Device Management Embedded Systems Service-Oriented Analysis In this course, you will

Course Tag

Web Service Microservices Representational State Transfer (REST) Service-Oriented Architecture

Related Wiki Topic

Article Example
Web-oriented architecture Enterprise Web Oriented Architecture (EWOA) is a sub-style of Enterprise Service Oriented Architecture (ESOA).
Service-oriented architecture A service-oriented architecture (SOA) is a style of software design where services are provided to the other components by application components, through a communication protocol over a network. The basic principles of service oriented architecture are independent of vendors, products and technologies.
Service-oriented architecture There are no industry standards relating to the exact composition of a service-oriented architecture, although many industry sources have published their own principles. Some of these
Service-oriented architecture A manifesto was published for service-oriented architecture in October, 2009. This came up with six core values which are listed as follows:
Collaboration-oriented architecture Collaboration Oriented Architecture (COA) is a computer system that is designed to collaborate, or use services, from systems that are outside of the operators control. Collaboration Oriented Architecture will often use Service Oriented Architecture to deliver the technical framework.
Service-oriented architecture Another major problem faced by SOA is the lack of a uniform testing framework. There are no tools that provide the required features for testing these services in a Service Oriented Architecture. The major causes of difficulty are:
Aspect-oriented software development The approach is implemented as a service in YAWL based on Service Oriented Architecture.
Web-oriented architecture Web-oriented architecture (WOA) was coined in 2006 by Nick Gall of the Gartner’s group. It is a software architecture style that extends service-oriented architecture (SOA) to web-based applications.
Semantic service-oriented architecture A Semantic Service Oriented Architecture (SSOA) is an architecture that allows for scalable and controlled Enterprise Application Integration solutions. SSOA describes a sophisticated approach to enterprise-scale IT infrastructure. It leverages rich, machine-interpretable descriptions of data, services, and processes to enable software agents to autonomously interact to perform critical mission functions. SSOA is technically founded on three notions:
Service-oriented architecture Service-oriented modeling is an SOA framework that identifies the various disciplines that guide SOA practitioners to conceptualize, analyze, design, and architect their service-oriented assets. The Service-oriented modeling framework (SOMF) offers a modeling language and a work structure or "map" depicting the various components that contribute to a successful service-oriented modeling approach. It illustrates the major elements that identify the "what to do" aspects of a service development scheme. The model enables practitioners to craft a project plan and to identify the milestones of a service-oriented initiative. SOMF also provides a common modeling notation to address alignment between business and IT organizations.
Service-oriented device architecture The purpose of service-oriented device architecture (SODA) is to enable devices to be connected to a service-oriented architecture (SOA). Currently, developers connect enterprise services to an enterprise service bus (ESB) using the various web service standards that have evolved since the advent of XML in 1998. With SODA, developers are able to connect devices to the ESB and users can access devices in exactly the same manner that they would access any other web service.
Service-oriented architecture Service-oriented architecture can be implemented with Web services. This is done to make the functional building-blocks accessible over standard Internet protocols that are independent of platforms and programming languages. These services can represent either new applications or just wrappers around existing legacy systems to make them network-enabled.
Service-oriented architecture In SOA, services use protocols which describe how they pass and parse messages using description metadata. This metadata describes both the functional characteristics of the service and quality-of-service characteristics. Service-oriented architecture aims to allow users to combine large chunks of functionality to form applications which are built purely from existing services and combining them in an ad hoc manner. A service presents a simple interface to the requester that abstracts away the underlying complexity acting as a black box. Further users can also access these independent services without any knowledge of their internal implementation.
Service layer In software design, for example Service-oriented architecture, the concept of service layer has a different meaning.
Service-oriented development of applications is a way of producing service-oriented architecture applications. Use of the term SODA was first used by the Gartner research firm.
Service-orientation Service-orientation has continued to receive increased recognition as an important part of the service-oriented computing landscape and a valid design approach to achieving service-oriented architecture.
Event-driven architecture Event-driven architecture can complement service-oriented architecture (SOA) because services can be activated by triggers fired on incoming events.
Open Grid Services Architecture Open Grid Services Architecture (OGSA) describes a service-oriented architecture for a grid computing environment for business and scientific use.
Service-oriented modeling Service-oriented modeling is the discipline of modeling business and software systems, for the purpose of designing and specifying service-oriented business systems within a variety of architectural styles and paradigms, such as application architecture, service-oriented architecture, microservices, and cloud computing.
Service-oriented architecture A primary challenge faced by service-oriented architecture is managing of metadata. Environments based on SOA include many services which communicate among each other to perform tasks. Due to the fact that the design may involve multiple services working in conjunction, an Application may generate millions of messages. Further services may belong to different organizations or even competing firms creating a huge trust issue. Thus SOA governance comes into the scheme of things.