Seggregating one application to differnt application

Hello Guys,

 

Today I am going to discuss regarding segregating a single application to different applications on the basis of user type, functionalities etc. Its not an easy task and require lot of planning and development efforts for any customer having an already live application to segregate their appln in two or three differnt application.  Now you may ask WHY? Whats the need of doing this?

 

Here lies the answer with example. Say, your application has mix type of users - Sales, Service, Distributors with specific functionalities. In the past you observeed, with you old architecture, some process were hangigng and it was not identifiable why these processess were getting bad and who is responsible for this - sales, service or distributor?

 

With new architecture you have seperate URLs for Sales, Service and Distributors logging and hitting their own object managers on to their respective hardwares. This is an approach I have collected from a live experience sometime back.

Lots of tasks were involved doing so. Few are discussed below very briefly:

 

1) Development Efforts:  Seggregaion is not an easy task and involve lot of developmet efforts on the basis of identifying the specific functionalities required by specific user group (or new appln). I would say for a live productionsetuop it would range from 1 to 3 months depenmding upon the kind of customization and development efforts.

 

2) New Architecture capacity planning: Again, you have to treat this altogether as a new project. Each appln has specific set of users and has their own concurrent annd active user load. Differnt sizings need to be performed for hardwares for each newly created application. Require some 5-10 days of rigrous planning based on concurrent user load and monitoring patterns and differnt parameters that need to be planned.

 

3) Tuning Application:  Once you are live in production you application may perform as you expected, but may differ and further require tuning. This is an ongoing activity and should be done after each major functionality Go-Live.

 

4) Issues resolution: Segregation may help isolate the originating point of any issue in this kind of environment where there are differnt category of users accessing these applications. Further analysis could be done based on logs available and other techniques.