architecture - Replacing Custom DAO Code With Web Service Calls -


In most of our webapps, we use a three-level architecture: Controller / Viewer, Service, and DAO Layers However, in most of the webapps, we use a three-level architecture:

What I like to do is create a general schema for all the departments that will use all the apps (yes, this is already the case but it is not ...) then I will be on the app server I would like to slap a simple web service, whose work is only to reach that common table. Instead of custom DAO codes, dedicated model objects, etc., the information will be obtained by simply calling webservice, possibly in JSON format.

However ... I have to know the answers to some questions:

  1. Is this really a cost effective idea? We might make about 10 small to medium projects (new or rewrite of the legacy app) for the financial year of each of our companies.
  2. If most of the departments (DO), DELETE (), and FindByName () / Find BIID () methods in the department DOO, will the code / effort be reduced significantly by changing the amount of code with the web service code? (Note that there should be written code for converting JSN results to convert box, etc.)
  3. Will the security implication of the web service call be a nightmare? In short, is it worth it in terms of manpower cost / maintenance / etc?

Common schemas for all systems are often not realistic

This is probably It's okay to improve as much as you are developing, but the cost of making changes is so great that it is not possible to make any changes.

Pattern "Backing Context" for a solution for this, this is a good description of Eric Evans's Domain Drivin Design Book


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -