By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,395 Members | 2,541 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,395 IT Pros & Developers. It's quick & easy.

Big Desktop Database Application - Architecture Help needed

P: 2

I am designing a .NET database application that uses 3 tier architecture. Starting initially, this application will be desktop application but I will convert it into a website later but design that I am planning should support both version.

Development Environment : VS2008, C#
Currently Database supported are MS SQL Server 2005 and MYSQL 5 and design for database support is extensible.

This application contains several high level modules (HLM) that can either share the data from the database of other high modules and some are totally independent modules.

Like say finance and project automation are not dependent on each other but finance and investments are. These are some examples of the modules that will be used in this the application.

For website version of this app,
Main Website will <mainapplication>.com and
High level module (HLM) will be having subdomain names like
<HLM1>.<mainapplication>.com ,
<HLM2>.<mainapplication>.com and so on.

Database Name : <mainapplication>

Now for desktop version should I create different <HLM> EXE application and linked them to the main application and share the same database with all the apps?

I like the design of MS Money application for desktop application. However, this is only a finance application and it is also that big. Can that design help me for this scenario or are there any references of big desktop application that is extensible and contains support for database ?

Currently I have research enough on desktop application for
1. Interprocess communication can be using named pipes, since it is on same machine.
2. Single Sign on in main application will allow access to other HLM exe application.
3. Only Main application will call the other HLM application. Running HLM Exe alone will give a error .
4. New HLM application will have a module code and store in the database and loaded in the main application once logged in. Using module code, the HLM exe will be loaded.
5. Main application will have framework to support dynamic linking of HLM and have base libaries that will be implemented and use by HLM exe application.
6. Each HLM exe will have its seperate BO and DAO layers.
7. If HLM B depends on HLM A then HLM B will reference HLM A BO layer for calling functionalities that are required.
8. There will be only 1 instance of the any application running at anytime time.

I am not sure of the following
1. Transaction handling between multiple processes.
2. If there are anything else that I need to take care of

Can anyone please help me decide and answer the queries (marked in Italic) so that I can move with the development of the application. This will be big application should the design and architecture should be finalize first.
Jul 24 '08 #1
Share this Question
Share on Google+
1 Reply

Expert 2.5K+
P: 4,871
I don't believe that it is reasonable to go on a free forum and ask for a design/ consultation. Our experts give freely of their time and there are limits to the services we can provide. Suggest either listing this in the jobs section to obtain quotes or hire a consultant, when this is required for an application of this size.

I suggest you read the Posting Guidelides. I am closing this thread.

Jul 24 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.