SERVICE ORIENTED ARCHITECTURE (KCS079)
Time: 3 Hours | Maximum Marks: 100
SECTION A (10 × 2 = 20 Marks)
(Attempt all questions in brief)
1(a) Latency calculation with orchestration overhead
Five services × 150 ms = 750 ms Orchestration overhead = 10% of 750 = 75 ms
Total latency = 750 + 75 = 825 ms
1(b) Compare WSDL, SOAP, and UDDI WSDL: Describes service interface and operations
SOAP: Messaging protocol using XML UDDI: Service registry for discovery
1(c) Availability = 99.9%, allowable downtime per year
Total hours/year = 365 × 24 = 8760 hours Downtime = 0.1% of 8760
Allowable downtime = 8.76 hours/year
1(d) Design process of client services in SOA
Client services are designed by identifying service consumers, defining interfaces, handling message formats, ensuring loose coupling, and implementing service invocation logic.
1(e) Technologies for service integration
Technologies include ESB, REST, SOAP, APIs, message queues, adapters, and middleware platforms for integrating heterogeneous systems.
1(f) Orchestration overhead calculation
Service latency (assume negligible) + orchestration overhead
Given overhead = 20 ms Total latency = 20 ms
1(g) Payback period calculation
Implementation cost = $1.5 million Annual savings = $500,000
Payback period = 1,500,000 / 500,000 Payback period = 3 years
1(h) Role of service orientation in Big Data analytics
Service orientation enables modular analytics, scalable data pipelines, reusable processing services, and integration of heterogeneous data sources.
1(i) Best practices for SOA strategy
Key practices include loose coupling, service reuse, standardized interfaces, governance enforcement, security integration, and continuous monitoring.
1(j) Defect reduction calculation
Initial defects = 10% of 10,000 = 1000 Final defects = 2% of 10,000 = 200
Defect reduction = 800 defects
SECTION B (Attempt any THREE) (3 × 10 = 30 Marks)
2(a) Evolution of SOA and MSA
SOA evolved to integrate enterprise systems through reusable services.
MSA (Microservices Architecture) further decomposed services into independently deployable units.
Drivers:
SOA: Integration, reuse, governance MSA: Scalability, agility, DevOps compatibility
Modern enterprises often combine both.
2(b) Composite applications & latency calculation
Composite applications integrate multiple services into a single workflow.
Latency = 120 + 100 + 80 Total latency = 300 ms
2(c) Strategic architecture governance
Governance defines policies, standards, monitoring, and lifecycle management.
It reduces downtime by enforcing SLA compliance, version control, and proactive monitoring.
2(d) Future trends in Big Data + SOA
Trends include AI-driven orchestration, event-driven services, cloud-native SOA, and real-time analytics.
Impact: faster decision-making and scalable processing.
2(e) Governance best practices & compliance
Best practices include policy enforcement, audit trails, access control, and documentation.
They ensure regulatory compliance and consistent service behavior.
SECTION C (Attempt any ONE) (10 Marks)
3(a) Challenges in adopting SOA in legacy systems
Challenges: Tight coupling
Lack of documentation High migration cost
Solutions: Service wrappers
Phased migration API gateways
Financial impact:
Initial cost is high, but long-term savings occur through reuse and reduced maintenance.
3(b) Why MSA is preferred & fault isolation comparison
MSA isolates faults at service level, preventing system-wide failure.
SOA may propagate faults due to shared infrastructure.
MSA provides better resilience in distributed systems.
