How to get up to speed on SOA?

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 9 years ago. I've been given the task of laying the groundwork of a SOA for my client. The goal is to open up various processes in an end-client independent way and also to make data available offline e.g. for reps visiting customers. I do have extensive experience with J2EE (Websphere) and web services but I would appreciate advice on how to build up such an SOA. Where are the pitfalls? What about security? How finely granulated should services be? etc. Links to tutorials and book recommendations would also be useful. Thanks! JavaScript questions and answers, JavaScript questions pdf, JavaScript question bank, JavaScript questions and answers pdf, mcq on JavaScript pdf, JavaScript questions and solutions, JavaScript mcq Test , Interview JavaScript questions, JavaScript Questions for Interview, JavaScript MCQ (Multiple Choice Questions)

Answer 1

Pitfalls Versioning/backwards compatibility: it gets really hard to change a contract once you have loads of clients. I have seen many sites version the APIs by introducing the version in the URL Granularity Each service should be reasonly self-contained (don't expect people to do 3 calls before they get what they need) Platform Independence Try to give more than one way of accessing your APIs (WS, JSON, REST...)