Article Info

Related Articles

How to handle exceptions

how to handle exceptions

How to collect and display statistic

how to collect and display statistic

Article Feed

On the way to SOA

foundation services diagram
Fig. 1. Foundation services

In one of the companies I used to fork for, a great amount of standalone applications and subsystems took place. This situation was caused on the first place by the size of the company and the lack of the single IT solution for the whole company as well as the single approach to the development of the software. Every time when one the developers teams was getting a new task to develop the application, the new Exception handling, system access control as well as audit and other general modules had to be developed (or the ones which were developed earlier were to be used as an option). This is considered to be the issue on the managerial level and generally the wrong approach of the projects. Here is another example. The new company starts up a new project. The developers are facing the same problem, which is the default of technical services or the lack of time for them to be developed, as the fast decision for the business has to be taken. As the result the decision is taken by the team to develop them later. Obviously there are plenty of useful products of logistics, audit, access control etc. But all of these products must be explored and forced to work together and it’s not proven, that the companies which developed these components will continue to support them. Thus I decided to create the basic or foundation, integrated with each other services to help myself as well as to help others who might be interested. These services include (as shown in Fig. 1.): Cache Services, Content Management Services, Culture Info Services, Date and Time Synchronization, Logging, Audit and Exception Resolution Services, Membership, Notification Services, Settings Services, State Management Services, Statistics Services and others…