Everyone talks about REST and GraphQL, but at Amdocs I spent significant time building SOAP-based web services. Here's why enterprise telecom still relies on XML-based protocols, and what I learned integrating legacy BSS/OSS systems.

The Challenge

JCOM's telecom infrastructure consisted of dozens of systems built across different decades. The billing system, provisioning platform, and customer management tools each spoke different protocols. Many core systems — particularly those handling subscriber provisioning and network activation — only exposed SOAP/WSDL interfaces. There was no option to "just use REST."

The Goal

I needed to build 5 new integration services connecting the Amdocs CRM to external BSS/OSS systems. These services needed to process 50,000+ daily transactions reliably, handle complex data structures that SOAP excels at (nested subscriber hierarchies, multi-step provisioning workflows), and maintain strict contract-first development with WSDL schemas.

The Approach

I adopted a contract-first approach, starting with WSDL definitions before writing any Java code. Using Apache CXF with Spring Boot, I generated Java stubs from WSDL files and implemented the business logic layer on top. For error handling, SOAP Faults provided structured error responses that downstream systems could parse programmatically — something REST APIs often handle inconsistently. I implemented WS-Security for authentication and WS-ReliableMessaging for guaranteed delivery on critical provisioning calls.

The Impact

All 5 services went live processing 50K+ daily transactions with 99.7% uptime. The contract-first approach meant zero integration issues at deployment — both sides had agreed on the exact data contract before a single line of business logic was written. The structured error handling through SOAP Faults reduced support tickets from integration issues by over 40%.

Key Takeaways

SOAP isn't dead — it's mission-critical in enterprise environments where strict typing, built-in security standards, and guaranteed delivery matter more than developer convenience. Contract-first development eliminates integration surprises. And understanding both REST and SOAP makes you significantly more valuable in enterprise engineering roles where legacy system integration is a daily reality.

Questions? kanade.pra@northeastern.edu