I was reading the stuff on Service Oriented Architecture (SOA) the other day as I thinking to have my application to run on that architecture so that I could provide an interface and able to "embed" my application to whatever platform.
The scenario that trigger my thought to develop my application in SOA is that many bloggers has already running their own blogs, isn't good that they have not move to my website but still able to interact with my application via the service embedded in their website?
I may not clear about the application I'm talking here, it is a information sharing application. Instead of having only one place (my website) to serve all users, why not allow all users consume my services at their own blogs and their able to share their information with others via my services. They are physically distributed but linked altogether. Of course, the website still serves as a platform to access all services. Users still have their own detail maintained in website. Again, the website also consumes the services, it just another interface.
I search in the Internet and find most of the articles discuss the history, design and benefit of using SOA. Most of them are pure text, I have problem with pure text; it is too much of information to read and digest, why not put it in a simpler way, like a diagram or something like that?
As far as I understand, SOA is simply a collection of interconnected web services. That's all. The benefit of SOA is that, the application could be port to any platform and to be consumed different way.
I'm look forward to develop my next web application in SOA.
No comments:
Post a Comment