Queuing in OneWay WCF Messages using Windows Service and SQL Server

Question

I need to implement a queuing mechanism for WCF service requests. The service will be called by clients in a one-way manner. These request messages should be stored in a SQL

Answer 1

1. If I were using MSMQ, clients could have forwarded the message to queue without knowing the service endpoint.

Yes - but they would need to know the MSMQ endpoint in order to send their message to the queue.....

But I am using SQL Server to store the request messages. How the clients can put the requests to SQL Server?

The clients won't put their requests into SQL Server - that's what the service on the server will do. The client just call a service method, and the code in there will store the request into the SQL Server table.

2. Is the solution feasible? Do we have any article/book that explains how to implement the above?

Sure, I don't see any big issue. The only point unclear to me right now is: how will the clients know their results?? Do they need to go get results from another service or something??

3. What are the steps to prevent service and client reaching faulted state in this scenario?

As always - just make sure your service code catches all exceptions and either handles them internally, or returns interoperable SOAP faults instead of .NET exceptions.