Designing with or without a services layer
Posted: Wed May 23, 2007 9:04 am
I've seen some companies who actually build their entire application based on a SOAP api. So basically all of the logic is in the API, then they build their own site on top of the API.
I was wondering what you think about this type of development, I could see it being a really smart way if you ultimately will have an API for 3rd parties and would want them to have the same functionality you have, but what if your not planning on having a public API? or what if you might have a public API but only a few functions..
Just would like to know what pros and cons you see in doing this... For Pros, I see the obvious, easily portable. But for cons, I see that it's potentially slower and will require more development.
I was wondering what you think about this type of development, I could see it being a really smart way if you ultimately will have an API for 3rd parties and would want them to have the same functionality you have, but what if your not planning on having a public API? or what if you might have a public API but only a few functions..
Just would like to know what pros and cons you see in doing this... For Pros, I see the obvious, easily portable. But for cons, I see that it's potentially slower and will require more development.