(SEM VII) THEORY EXAMINATION 2022-23 SERVICE ORIENTED ARCHITECTURE

SECTION A (2 Marks Each)

(a) Microservice Architecture

Microservice architecture is an architectural style where an application is built as a collection of small, independent services, each performing a specific business function and communicating through APIs.

(b) Contemporary SOA

Contemporary SOA is a modern form of SOA that integrates web services, cloud computing, REST, microservices, and messaging systems to build flexible and scalable applications.

(c) SOA Reference Architecture

SOA reference architecture is a standard blueprint that defines layers, components, relationships, and best practices for designing service-oriented systems.

(d) SOAD

SOAD stands for Service Oriented Analysis and Design, a methodology used to analyze business requirements and design reusable services.

(e) Orchestration in Web Services

Orchestration refers to the coordination and control of multiple web services to execute a business process in a predefined sequence.

(f) Strategic Architecture Governance

It ensures that SOA implementations follow standards, policies, best practices, and business goals through proper control and monitoring.

(g) Principle of Service Orientation

Service orientation is based on principles like loose coupling, reusability, abstraction, interoperability, and autonomy.

(h) Goals of Service-Oriented Analysis

The goals include identifying reusable services, aligning IT with business needs, improving flexibility, and reducing system complexity.

(i) Derived Business Services and Benefits

Derived business services are created by combining existing services. Benefits include reusability, faster development, and reduced cost.

(j) Technology for Big Data

Big Data technologies include Hadoop, Spark, NoSQL databases, distributed storage, and cloud computing for handling large-scale data.

SECTION B (10 Marks Each – Attempt Any Three)

(a) Service Layer Abstraction in SOA

Service layer abstraction hides internal service logic and exposes only required interfaces to consumers. This improves security, flexibility, and reusability. Consumers interact with services without knowing implementation details, enabling independent service evolution.

(b) Comparison between SOA, Client-Server, and Distributed Internet Architecture

SOA uses loosely coupled reusable services, while client-server architecture depends on tight coupling between client and server. Distributed Internet architecture focuses on scalability but lacks standardized service reuse like SOA. SOA supports interoperability and business process integration.

(c)

(i) Orchestration in Web Services
Orchestration controls the execution flow of multiple services using a central coordinator, often implemented using BPEL.

(ii) Security Specification Used in SOA
Security in SOA uses standards like WS-Security, SSL/TLS, OAuth, SAML, and authentication mechanisms to protect services.

(d) SOA Reference Architecture

SOA reference architecture consists of layers such as service consumer, service provider, service registry, business process layer, integration layer, and governance layer. It ensures standardization and efficient service interaction.

(e) Design of Business Process Services

Business process services coordinate multiple services to achieve business objectives. They define workflows, rules, service interactions, and exception handling.

SECTION C (10 Marks Each)

Q3

(a) SOAP and WSDL

SOAP is a protocol for exchanging structured information using XML over HTTP. WSDL describes web service interfaces, operations, and message formats. Together, they enable standardized communication between distributed services.

(b) SOA Governance and Challenges

SOA governance manages policies, standards, security, versioning, and service lifecycle. Challenges include complexity, policy enforcement, service version control, and organizational resistance.

Q4

(a) Components of SOA and Their Functions

Key components include service provider, service consumer, service registry, ESB, orchestration engine, and governance framework. These components enable communication, discovery, and management of services.

(b) Messaging Patterns in SOA with SOAP

SOAP supports request-response, one-way messaging, publish-subscribe, and asynchronous messaging patterns for reliable service interaction.

Q5

(a) Features and Pitfalls of Contemporary SOA

Features include loose coupling, reusability, scalability, interoperability, and cloud integration. Pitfalls include high complexity, governance overhead, performance issues, and poor service design.

(b) Messaging Patterns Used in SOA

Common patterns include synchronous, asynchronous, request-reply, and event-driven messaging using SOAP envelopes.

Q6

(a) Service Activity Structure in Web Services

Service activity structure defines operations, message flow, execution sequence, and interactions among services within a business process.

(b) Task-Centric Business Service Design

Task-centric design focuses on specific business tasks. For example, an “Order Processing Service” handles validation, payment, and confirmation as a single business task.

Q7

(a) Native Web Service Support for Service Orientation

Web services support service orientation through standards like SOAP, WSDL, UDDI, HTTP, and XML, enabling loose coupling and interoperability.

(b) Metadata and Its Importance in WSDL

Metadata describes service operations, data types, bindings, and endpoints. In WSDL, metadata helps consumers understand how to access and use services correctly.