We are actually running a very small 3 year old business in the arts and education industry and we have about 15 employees. Our company does not own any IT systems at all. Even the company website is hosted by a third party web hosting company.
Being one of the more IT-inclined personnel, I was roped in by my boss recently to consider implementing certain systems to replace some processes which, until now, were done in a very traditional and manual way. One of the suggestions that my boss came up with was a CRM system to help some of my colleagues handle the customers.
Now, I have been reading and I realized that SOA has great promises and potential, so I decided to take a look at it. I realized that one of the ways SOA can help companies deliver more business value was in re-structuring the way their layers of legacy systems and technologies interact.
Since my company has just started to pay more attention to utilizing IT, I was wondering to myself: Why not adopt SOA right from the start and slowly build our systems in the SOA way? So I started reading up more and more about SOA. I realized that to truly make this approach a successful one, efforts will have to be put into the business modeling, identify the services, come up with a sound SOA governance policy, not to mention the need for a reliable messaging platform, service bus etc. All these are too much overhead for me. If I were to design and implement the CRM system in the traditional way, it is definitely going to take me much lesser time. However, I cannot neglect the fact that SOA is going to bring in benefits in the long run, since it is highly possible that we are going to need more IT systems in the future.
My question is: Is it worth the effect for my company to adopt SOA at this point in time when we are just starting to use IT? If it is, how should I go about doing it? Looking at the general model for implementation, it seems like too much work just to start off.
October 6, 2006 10:58 AM
December 4, 2007 8:36 PM