Distributed System in .NET

Question

0.00/5 (No votes)

See more:

Let us say we have a project which is three layered. Assume that the data layer is on server1(let us say its in India), Business Logic layer is on server2(lets say its in US) and the user interface/web services are on server3. All servers are at different locations geographically. Now the question is:-

1. How the lifetime of objects will be maintained?
2. How the State Management, both server & client side is going to be managed?
3. Can you give me some reference urls?

Regards,
Swaroop

Posted 13-Sep-11 21:26pm

swaroop1069

Add a Solution

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)

Mehdi Gholam · Answer 1 · 2011-09-13T22:15:00

Solution 1

It is not advisable or practical to break your application into geographic layers like this.

Keep the layers together on the same site and distribute or replicate your data as needed. This will make things faster for the user and easier for you to implement.

Posted 13-Sep-11 22:15pm

Mehdi Gholam