which technologies do you recommend for middleware server in .net?

Question

0.00/5 (No votes)

See more:

Hi,

I don't know whether this is a silly question!

I searched the web with no useful hits and I am a dot net user (C#).

I want to develop a Server, it may be called a middleware server (actually I am not sure), which does the following tasks:
I have a server which cannot be modified and many clients that request the server and receive the results.
I can modify the clients.

Now I want to develop software that receives client requests, checks if the server is busy or how many tasks are queued at the server, store the client requests to temporary database if server is busy, fetch requests queued in the temporary database and forward to the server and then receive the results and forward to to clients and the like.

The questions are

1. which technologies are best to use while remaining in dotnet, WCF, Webservives, remoting, or other?
2. how complex is this task assuming that there are tasks like transaction handling, load balancing, logging, security checking mechanisms and the like?
3. what things should i read to do these task, relevant books tutorials etc?
4.while searching I find such things as middleware in java but not in dotnet. what is the reason?

Posted 1-Sep-10 21:16pm

kebedetesema

Updated 1-Sep-10 21:52pm

Dalek Dave

v3

Add a Solution

Comments

Dalek Dave 2-Sep-10 3:52am

Edited for Readability.

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)

DaveAuld · Answer 1 · 2010-09-05T02:01:00

This should be relatively easy to do. The most complex bit will probably be deciding how you want to wrap up the jobs into something that can be persisted to the temporary database or sent onto the Server for processing.

You might want to look at creating a windows Service to handle the server end. and a standard windows application for the client end.

For the temporary database you could use MSSQLExpress or, depending on your job objects serialise.deserialise them to/from the filesystem.

For the communications you could use a variety of methods, either simple TCP sockets or look at some of the Web classes.

I don't think there is any justification to go down the MSMQ route or use remoting.