Intogueendobe
New Member
The company I work for is looking to redo our CRM, and a main point in our changes/design is a better way to centralize our business logic. We want to develop a clean API, but we're unsure of what route to take. We considered a SOAP based web service, but are worried that there will be too much overhead.We'd like to use the API for the CRM we're developing, as well as other internal applications that need access to the data. The CRM will be browser based similar to a program like SalesForce, and we develop in .Net. The other main applications that need access are our websites which will also be submitting/retrieving data from the API.Any suggestions on what route to take and the type of API to use that will be easy on our network bandwidth?EDIT: As mentioned below, I'm looking for suggestions for API design/technologies, not how to write the code or anything like that.