MCA 231 Service Oriented Architecture Notes are a 78-page printed book for GGSIPU MCA Semester 3 (Core Elective III, batch admitted 2025-26 onwards). All 4 units are covered, from the SOA triangle and XML Schema to Spring Boot, Spring Cloud and Docker, with 31 diagrams, 10 XML examples, 51 short-answer questions with answers and 36 long-answer plans.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the GGSIPU MCA Scheme of Examination and Detailed Syllabus (A.S. 2025-26 onwards, BoS 28 Jul 2025) · Updated 13 October 2026 · Editorial policy
Scheme: MCA (2 years), A.S. 2025-26 onwards | Applies to: batch admitted 2025-26 onwards | Verified against: MCA scheme and syllabus, BoS 28 Jul 2025
MCA 231 Service Oriented Architecture at a glance: GGSIPU MCA Sem 3 credits, units and exam pattern
MCA 231 is one of 11 papers offered in Core Elective III of the two-year MCA, and these MCA 231 Service Oriented Architecture IPU notes follow the official pattern below.
| Code and title | MCA-231 Service Oriented Architecture |
|---|---|
| Course and semester | MCA (2 years), Semester 3 |
| Category | Core Elective III (any one of MCA-227 to MCA-247) |
| Credits and weekly hours | 3 credits: 3 lecture hours, no tutorial |
| Units | 4 units, 10 teaching hours each |
| Marks and passing mark | 100 marks; passing marks 40 out of 100 |
| End-term pattern | Compulsory Q1 (12 marks) plus one of two questions per unit at 12 marks each (12 + 48 = 60 marks) |
| Internal and end-term split | Not printed in the official MCA PDF |
| Applies to | Batch admitted 2025-26 onwards |
| Paired lab | MCA-267 Lab based on Core Elective III (SOA Lab): 0-2, 1 credit |
It sits with the other GGSIPU MCA Semester 3 papers.
MCA 231 Service Oriented Architecture Notes unit-wise: 87 exam questions, 31 diagrams and 10 XML examples across 4 units
These GGSIPU MCA Sem 3 Service Oriented Architecture notes run to 78 pages, each unit ending with solved questions and a revision table. The official PDF numbers the units without titles, so the titles below are the ones in our notes. Notes for every other MCA paper sit under GGSIPU MCA notes.
MCA 231 Unit 1: SOA, Enterprise-Wide SOA, Service Oriented Applications and XML
Unit 1 (pages 5 to 25) is the longest unit. A bank counter explains what a service is; then come SOA vs microservices, the strawman and reference architectures (five horizontal, four vertical layers) and OOAD vs SOAD with IBM's SOMA. The XML half covers well-formed rules, namespaces, DTD and XSD. It has 20 sub-topics, 8 diagrams, all 10 XML examples, 12 short and 9 long questions.
| Symbol | Meaning | Example |
|---|---|---|
a? | Zero or one | (title, subtitle?) |
a* | Zero or more | (chapter*) |
a+ | One or more | (author+) |
(a|b) | Either a or b | (cash | card) |
Quick look: how a DTD controls how often an element appears (from page 20)
- Symbol
a?- Meaning
- Zero or one
- Example
(title, subtitle?)
- Symbol
a*- Meaning
- Zero or more
- Example
(chapter*)
- Symbol
a+- Meaning
- One or more
- Example
(author+)
- Symbol
(a|b)- Meaning
- Either a or b
- Example
(cash | card)
MCA 231 Unit 2: Service Oriented Analysis and Design, Big Data, SOA Governance and Best Practices
Unit 2 (pages 26 to 43) opens with Thomas Erl's eight design principles, then NFRs, the SLA and client, activity and data services. Technologies cover SOAP, WSDL, UDDI, REST, the ESB and WS-BPEL, followed by the 5 V's of Big Data, Hadoop, NoSQL and governance. It has 20 sub-topics, 9 diagrams, 15 short and 9 long questions.
| Basis | Orchestration | Choreography |
|---|---|---|
| Control | One central controller | No controller; agreed steps |
| Standard | WS-BPEL, BPMN engines | WS-CDL; events |
| Coupling | Tied to the orchestrator | Loose, through events |
| Error handling | Easy: orchestrator compensates | Harder: each party handles its part |
Quick look: orchestration vs choreography, two ways to coordinate services (from page 34)
- Basis
- Control
- Orchestration
- One central controller
- Choreography
- No controller; agreed steps
- Basis
- Standard
- Orchestration
- WS-BPEL, BPMN engines
- Choreography
- WS-CDL; events
- Basis
- Coupling
- Orchestration
- Tied to the orchestrator
- Choreography
- Loose, through events
- Basis
- Error handling
- Orchestration
- Easy: orchestrator compensates
- Choreography
- Harder: each party handles its part
MCA 231 Unit 3: Microservices Architecture, Cloud, HoneyComb and Spring Boot Microservices
Unit 3 (pages 44 to 62) has the most sub-topics. Monolith, SOA and microservices are compared in one table, then cloud models and the HoneyComb analogy. The hands-on half builds a Spring Boot greeting service, a Customer CRUD service, HATEOAS links, WebFlux with Mono and Flux, security, CORS and actuators. It has 22 sub-topics, 6 diagrams, 12 short and 10 long questions.
Quick look: the smallest Spring Boot REST endpoint (from page 53)
@RestController
public class GreetingController {
@GetMapping("/")
public Greet greet() {
return new Greet("Hello World!");
}
}Output: GET localhost:8080/ returns {"message":"Hello World!"}, because @RestController writes the return value into the response body as JSON.
MCA 231 Unit 4: Scaling Microservices with Spring Cloud, Docker Containers and Cloud SOA Case Study
Unit 4 (pages 63 to 78) maps Spring Cloud component by component (Config Server, Eureka, OpenFeign, Gateway, Resilience4j, Sleuth with Zipkin) on the BrownField airline PSS, then containerises it with Docker, Compose, RabbitMQ, registries and Kubernetes, ending with a cloud SOA case study. It has 10 sub-topics, 8 diagrams, 12 short and 8 long questions.
Quick look: a Dockerfile for the Fares microservice (from page 70)
FROM eclipse-temurin:17-jre-alpine
WORKDIR /app
COPY target/fares-1.0.jar app.jar
EXPOSE 8080
ENTRYPOINT ["java", "-jar", "app.jar"]Result: docker build -t brownfield/fares:1.0 . creates the image and docker run -d -p 8080:8080 starts it as a container.
Publish, Find and Bind in service oriented architecture: excerpt from page 9 of the MCA 231 notes
Excerpt from page 9 (Unit 1, section 1.5), rewritten for the web.
The conceptual model of SOA shows who takes part in a service interaction and what passes between them. It is usually drawn as the SOA triangle of Publish, Find and Bind.
Roles in the conceptual model
- Service provider: owns and hosts the service. It implements the service, writes its description (the contract) and publishes that description to the registry.
- Service registry (broker): a searchable directory of service descriptions. In classic web services this is UDDI; in microservices it is a discovery server such as Eureka.
- Service consumer (requestor): the application or service that needs a capability. It finds the description in the registry and then binds to, or invokes, the provider.
Operations in the model
| Operation | Who does it | What happens | Web-service standard |
|---|---|---|---|
| Publish | Provider to registry | The service description (interface, location, policies) is registered | WSDL stored in UDDI |
| Find (discover) | Consumer to registry | The consumer searches by name or category and gets the description | UDDI inquiry API |
| Bind (invoke) | Consumer to provider | The consumer connects to the endpoint and exchanges messages | SOAP over HTTP |
The three operations of the SOA triangle (excerpt, page 9)
- Operation
- Publish
- Who does it
- Provider to registry
- What happens
- The service description (interface, location, policies) is registered
- Web-service standard
- WSDL stored in UDDI
- Operation
- Find (discover)
- Who does it
- Consumer to registry
- What happens
- The consumer searches by name or category and gets the description
- Web-service standard
- UDDI inquiry API
- Operation
- Bind (invoke)
- Who does it
- Consumer to provider
- What happens
- The consumer connects to the endpoint and exchanges messages
- Web-service standard
- SOAP over HTTP
Other elements of the model
The service contract is the formal agreement on operations, message formats, data types and policies, written as WSDL plus XSD. The service interface is the endpoint and the operations exposed to the outside world, while the service implementation (the code and data behind it) stays hidden from consumers.
Messages are the requests and responses, usually XML in SOAP or JSON in REST. The Enterprise Service Bus is the middleware that routes, transforms and mediates messages between consumers and providers. Service policies and the SLA fix rules for security, reliability, response time and availability, and a business process (for example in BPEL) coordinates several services to finish one business task.
Do the MCA 231 notes cover the full GGSIPU syllabus?
Yes. Every topic listed for MCA-231 in the official 2025-26 syllabus has its own section in the notes, from service orientation in daily life to the cloud SOA case study.
| Official unit | Official topics | Where in the notes | Status |
|---|---|---|---|
| Unit I | SOA; Enterprise-Wide SOA (strawman, reference architecture, OOAD, SOAD); Service Oriented Applications | Sections 1 to 3, pages 6 to 15 | Covered |
| Unit I | XML: advantages, well formed XML, namespaces, DTD, schema | Section 4, pages 16 to 23 | Covered |
| Unit II | Service Oriented Analysis and Design; Technologies for SOA (enablement, integration, orchestration) | Sections 1 to 2, pages 27 to 35 | Covered |
| Unit II | Big Data and SOA; SOA Governance and Implementation; SOA Best Practices | Sections 3 to 5, pages 35 to 41 | Covered |
| Unit III | MSA; Cloud and Microservices Architecture; HoneyComb | Sections 1 to 3, pages 45 to 51 | Covered |
| Unit III | Building Microservices with Spring Boot; Applying Microservices Concepts | Sections 4 to 5, pages 51 to 59 | Covered |
| Unit IV | Scale Microservices with Spring Cloud Components (BrownField PSS, Spring Cloud Config) | Section 1, pages 64 to 67 | Covered |
| Unit IV | Containerizing Microservices with Docker; A case study on Cloud SOA | Sections 2 to 3, pages 68 to 76 | Covered |
Official MCA-231 topics mapped to sections and pages of the notes
- Official unit
- Unit I
- Official topics
- SOA; Enterprise-Wide SOA (strawman, reference architecture, OOAD, SOAD); Service Oriented Applications
- Where in the notes
- Sections 1 to 3, pages 6 to 15
- Status
- Covered
- Official unit
- Unit I
- Official topics
- XML: advantages, well formed XML, namespaces, DTD, schema
- Where in the notes
- Section 4, pages 16 to 23
- Status
- Covered
- Official unit
- Unit II
- Official topics
- Service Oriented Analysis and Design; Technologies for SOA (enablement, integration, orchestration)
- Where in the notes
- Sections 1 to 2, pages 27 to 35
- Status
- Covered
- Official unit
- Unit II
- Official topics
- Big Data and SOA; SOA Governance and Implementation; SOA Best Practices
- Where in the notes
- Sections 3 to 5, pages 35 to 41
- Status
- Covered
- Official unit
- Unit III
- Official topics
- MSA; Cloud and Microservices Architecture; HoneyComb
- Where in the notes
- Sections 1 to 3, pages 45 to 51
- Status
- Covered
- Official unit
- Unit III
- Official topics
- Building Microservices with Spring Boot; Applying Microservices Concepts
- Where in the notes
- Sections 4 to 5, pages 51 to 59
- Status
- Covered
- Official unit
- Unit IV
- Official topics
- Scale Microservices with Spring Cloud Components (BrownField PSS, Spring Cloud Config)
- Where in the notes
- Section 1, pages 64 to 67
- Status
- Covered
- Official unit
- Unit IV
- Official topics
- Containerizing Microservices with Docker; A case study on Cloud SOA
- Where in the notes
- Sections 2 to 3, pages 68 to 76
- Status
- Covered
Official source: MCA Scheme of Examination and Detailed Syllabus, A.S. 2025-26 onwards. The notes follow its textbooks, including Kambhampaty for SOA and MSA and Rajesh RV for Spring.
Every course in GGSIPU notes is checked against its official PDF the same way.
How to write MCA 231 answers: architecture diagrams, XML snippets and twelve-mark case studies
Each MCA 231 unit question carries 12 marks, so every long question in the notes has an answer plan: which figure to draw, which table to add, where to stop. The Docker plan, for instance, runs Fig 4.5, concept table, Dockerfile, then build and run commands.
Draw first: the SOA triangle or the Spring Cloud ring anchors the answer in two minutes. Keep code short: a five-line XSD fragment proves the point. Close with a comparison table such as DTD vs XSD or VMs vs containers.
Worked example: "Discuss a case study on Cloud SOA"
Use the notes' six headings, filled in for BrownField Airline:
- Background and problem: a monolithic PSS.
- Goals: scaling search during fare sales.
- Architecture diagram: Fig 4.8.
- Implementation steps: the split into Search, Fares, Booking and Check-in.
- Benefits: a before and after table.
- Challenges and lessons: sagas for consistency.
Practise this structure on GGSIPU MCA important questions.
MCA 231 exam corner: 51 short-answer and 36 long-answer questions by unit
| Unit | Short-answer (with answers) | Long-answer (with answer plans) | Diagrams |
|---|---|---|---|
| Unit 1 | 12 | 9 | 8 |
| Unit 2 | 15 | 9 | 9 |
| Unit 3 | 12 | 10 | 6 |
| Unit 4 | 12 | 8 | 8 |
| Total | 51 | 36 | 31 |
Solved exam questions in the MCA 231 notes, unit by unit
- Unit
- Unit 1
- Short-answer (with answers)
- 12
- Long-answer (with answer plans)
- 9
- Diagrams
- 8
- Unit
- Unit 2
- Short-answer (with answers)
- 15
- Long-answer (with answer plans)
- 9
- Diagrams
- 9
- Unit
- Unit 3
- Short-answer (with answers)
- 12
- Long-answer (with answer plans)
- 10
- Diagrams
- 6
- Unit
- Unit 4
- Short-answer (with answers)
- 12
- Long-answer (with answer plans)
- 8
- Diagrams
- 8
- Unit
- Total
- Short-answer (with answers)
- 51
- Long-answer (with answer plans)
- 36
- Diagrams
- 31
The MCA 231 notes solve 51 short-answer questions and give answer plans for 36 long-answer questions across 4 units, backed by 31 diagrams and 10 XML examples.
One question per unit, with answer pointers:
- Unit 1: What is meant by loose coupling? Pointer: consumer and provider depend only on the contract, not on each other's code, platform or location.
- Unit 2: What is the CAP theorem? Pointer: a distributed store guarantees only two of Consistency, Availability and Partition tolerance; HBase is CP, Cassandra AP.
- Unit 3: What is HATEOAS? Pointer: a REST constraint where responses carry links (
_linksin HAL) to related resources and next actions. - Unit 4: What is a circuit breaker? Pointer: it opens after repeated failures, returns a fallback, then half-opens to test recovery (Resilience4j).
More practice sits in the MCA 231 important questions.
Who writes and checks the MCA 231 SOA notes?
- Prateek Talwar, author: Founder, Unnati Educations; Associate Company Secretary (ACS), ICSI, membership no. 58704, since 15 May 2019; B.Com, University of Delhi (School of Open Learning), 2012. Profile
- Ritik Rawat, subject reviewer: B.Tech; Senior Full Stack Developer, Unnati Educations, reviewing the MCA, BCA and B.Tech notes.
This 2026-27 edition maps to the MCA scheme approved by the USIC&T Board of Studies on 28 July 2025. Its code uses Spring Boot 3.2, Spring Cloud 2023.0 and Resilience4j. Updated 13 October 2026 under our editorial policy.
The same team prepares GGSIPU important questions for each course.
MCA 231 and the GGSIPU MCA Sem 3 papers it connects to
The paper list for all four terms is on the GGSIPU MCA syllabus page.
Paired lab: MCA-267, the lab based on Core Elective III (SOA Lab, 1 credit). Its four objectives follow the units:
- Build an XML document: Unit 1.
- Design REST services and web services: Unit 2 service enablement.
- Build RESTful services with Spring Boot: Unit 3.
- Implement Docker containers: Unit 4.
Alongside it sit MCA-201 Design and Analysis of Algorithms and MCA-203 Artificial Intelligence and Machine Learning; from Core Elective II, MCA-223 Cloud Computing overlaps most with Units 3 and 4. Java from MCA-109 matters most, as Units 3 and 4 use Spring code.
MCA 231 SOA notes FAQs
How do I get the full MCA 231 notes?
Tap "Get Full Notes" and send the pre-filled WhatsApp message to 9899436384. The MCA 231 notes are sold only as a printed book of 78 pages, not as a PDF. Once your order is confirmed on WhatsApp, the book is couriered to you, reaching you within 5 to 7 days at most, depending on your location.
Can I get the MCA 231 notes as a PDF instead of a book?
No. The full MCA 231 notes come only in printed book form; there is no PDF or soft copy edition. The one PDF on this page is the watermarked sample, which shows the cover, contents and one page from each unit. The printed book keeps the 31 diagrams and code listings easy to mark up.
What is the passing mark for MCA 231 Service Oriented Architecture?
MCA 231 is marked out of 100, and the end-term paper set under the official instructions totals 60 marks (12 + 48). The MCA scheme of examination states passing marks as 40 out of 100 for every paper; it does not print how the other 40 marks are split. For end-term minimums and re-appear rules, see Ordinance 11 on ipu.ac.in.
Which MCA 231 unit needs the most study time?
Unit 3 has the most ground to cover, with 22 sub-topics across 19 pages, from cloud models and the HoneyComb analogy to eight Spring Boot sub-topics with code. Unit 1 is the longest at 21 pages, and Unit 2 has the most short-answer questions (15, against 12 in each other unit). Unit 4 is the shortest at 16 pages but code-heavy, with Dockerfiles, commands and YAML.
Is MCA 231 compulsory in MCA Semester 3?
No. MCA 231 is one of 11 options in Core Elective III, carrying 3 credits and 3 lecture hours a week. The scheme adds that an elective with fewer than 20 students may still be offered without classes, and students then complete it through a MOOC with prior approval of the Programme Co-ordination Committee. Its practical partner is the MCA-267 lab.
Do the MCA 231 notes include Spring Boot and Docker code?
Yes. Unit 3 of the MCA 231 notes has a Spring Boot greeting service, a Customer CRUD service with Spring Data JPA, a HATEOAS response in HAL format and a WebFlux controller, plus CORS and actuator setup. Unit 4 adds Spring Cloud Config, Eureka and Feign code, a Dockerfile, Docker commands, a Compose file and RabbitMQ setup, with comments on key lines.
Get the full MCA 231 Service Oriented Architecture Notes on WhatsApp
What is inside the printed MCA 231 notes book
- Part
- Cover and contents
- Pages
- 1 to 4 (4)
- Questions
- -
- Part
- Unit 1
- Pages
- 5 to 25 (21)
- Questions
- 12 short + 9 long
- Part
- Unit 2
- Pages
- 26 to 43 (18)
- Questions
- 15 short + 9 long
- Part
- Unit 3
- Pages
- 44 to 62 (19)
- Questions
- 12 short + 10 long
- Part
- Unit 4
- Pages
- 63 to 78 (16)
- Questions
- 12 short + 8 long
These Service Oriented Architecture notes in English come as a printed book only, not a PDF. Delivery: within 5 to 7 days at most; the exact time may vary with your location.
Order the printed MCA 231 notes book on WhatsApp (4 units, 78 pages)
Unnati Educations is an independent education provider based in Vikaspuri, Delhi. We are not affiliated with, authorised by, or endorsed by Guru Gobind Singh Indraprastha University (GGSIPU). 'GGSIPU' and 'IPU' are used only to describe the syllabus our notes follow. For official information, visit ipu.ac.in.
Ready for the full notes?
Discuss coverage and delivery with our team.