different modules as different projects

Question

0.00/5 (No votes)

See more:

any one can suggest me.

I have modules like HR,Accounts, Audits and Xyz..

present we are done with Accounts and another module Operation these are fuly dependent .
Ok , but now we want to develope HR Complete module with all futures , i where suggested to make different application with different database because HR Module should be like Serveice plug-in if any customer wants we have to give permisisions for HR if not dis service HR module .

If we take different data base and application how can we provide interface between two projects base on serveice required not required.

Thanks
karthik

Posted 19-Aug-11 23:54pm

karthikkushala

Add a Solution

Comments

Mehul M Thakkar 20-Aug-11 6:47am

Before posting question please make sure you have checked spelling & grammar.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-08-20T21:14:00

I see no justification for different projects at all. You can and usually should have different threads, different assemblies and make some assemblies as plug-ins loading them during run time, depending on configuration.

Splitting the solution into different processes adds good amount of hassles, but what would be the benefits? You would have some benefits if you need a potential for making the application distributed, scalable — adding more client and/or server computer, especially if you need to do this during run time, without stopping of your production. In other cases it would not make any sense. Here is one simple criteria: if you plan to use the whole application on one single computer (I do not count database servers here), there is no sense to make it multi-process. This is one more case when you need more than one process: for interoperability between 32-bit and 64-bit code — they cannot leave on a single process.

So, if you really need to make an application composed from different processes, you need to use, not surprisingly… IPC (Inter-Process Communication), see http://en.wikipedia.org/wiki/Inter-process_communication[^].

In .NET it can be classical remoting or WCF. Learn about it.

—SA