We currently have a SOAP based web service which is being used by various teams as the primary data source. We eventually want to transition to REST based services. We are reluctant to do this now as the clients would have to do changes.

What can we do to make this transition smooth?

  • 1
    recommended reading: Why is asking a question on “best practice” a bad thing? – gnat Dec 16 '13 at 12:55
  • Is the back-end well separated from the soap interface? Do you need to make big structural changes to the back-end to add this new rest interface? – Luc Franken Dec 16 '13 at 18:56
  • Back end is pretty much separated from the soap interface. No major changes needed there. It is the client side changes that worries us. – Siddharth Dec 17 '13 at 6:54

Don't replace, add.

When you achieve feature parity, stop making updates to the SOAP API and declare it deprecated.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.