Breathing new life into legacy SOAP services
The reality is that SOAP services are no longer cool. Developers today want to integrate with APIs that are labelled REST. They want descriptive URLs, JSON payloads and familiar HTTP status codes. But many enterprises spent 10 years building SOAP services and many of those services are working just fine today. Rewriting them would be a huge effort with the risk of minimal gain. The good news is that it is possible to give developers what they are looking for without a re-write. You can take advantage of HTTP's layered architecture to put a façade in front of your SOAP services, re-use all your existing code, breathe new life into your service and still support the existing client applications that are happily sending SOAP messages.This talk will explore the process of transforming native HTTP requests into SOAP messages and back into native HTTP responses. We will discuss which parts of the façading process can be automated and which parts require design decisions. Finally we will explore what capabilities we gain with this new style of API, and what we lose, so that you can make an informed decision on the future of your SOAP services.
Darrel is a software developer at Microsoft working for the Azure API Management team. He has been building distributed business applications on the Microsoft platform for more than 20 years. He is an active member of the .NET community and OSS contributor. He is a member of the OAI TDC, working on the next version of the OpenAPI specification and recently joined the Microsoft OneAPI Council, who are responsible for providing API design guidelines within Microsoft and to the Microsoft ecosystem. He co-authored the O'Reilly book, Designing Evolvable Web APIs with ASP.NET.