Skip to main content

Message reliablity


When a message is sent across the network many things can go wrong. The message can be lost, dropped or sent in wrong order. This can happen due to a variety of reason, network failure, network congestion and proxy failure are few reasons among many other reasons. 

WCF Reliablity features sessions are used to take care most of the above issues. There are two types of reliability Message reliability and Transport reliability. These reliability features simplifies coding needed.

Enabling reliable session

Reliable sessions are built on top of SOAP messaging and enables connection maintenance, verification and message ordering. Turning on reliable session allow the application to ignore duplicates, retry dropped connection and reestablish connections, notify service when the client is not available anymore. However, the cost of this reliability is increased traffic.

Reliable session is easy to turn on. For some binding the reliable session is on by default whereas for other binding its off by default.
  • wsHttpBinding          - default is off
  • netTcpBinding           - default is off
  • wsDualHttpBinding    - default is on
1. Open the WCF service application that you created earlier or download start file here.

2. To make a session reliable, open the App.config of the host and add the following updates to the the binding configuration. 

        <bindings>
          <wsHttpBinding>
            <binding name ="WsHttpBindingConfig">
              <reliableSession />
            </binding>
          </wsHttpBinding>
        </bindings>

3. To order the messages set the ordered property to true. 
<reliableSession ordered="true" /> 

Enabling Queued Messaging 

Enabling message queues makes the message persist until the message is successfully transferred across the wire. This allows asynchronous communication between the client and the server. This means the services and the client that consume that service do not have to be up and running at the same time making service host and client to be loosely coupled. Such feature is ideal in scenarios where the service may have to serve a huge loads temporarily.

4. To enable queued messages, first we need a queue. To create a queue, MSMQ should be installed. To check, open Computer Management and check if there is Message Queuing under Services and Applications. If not you will have to install MSMQ, do step 5, or else do step 8.

5. Open Control Panel (Win key + X > select Control Panel) > Programs > Programs and Features > Turn Windows features on or off > Expand Microsoft Message Queue (MSMQ) Server Core > check MSMQ HTTP Support >  click OK

6. Open Computer Management, expand Services and Applications, Expand Message Queuing > right click on Private Queues > select New > Private Queue > type productservice > click OK.

7. To use MSMQ with WCF you have to ensure that all the contract is marked OneWay. When using endpoint configured to use MSMQ, it is important to ensure all the operationcontract is marked IsOneWay=true. Update OperationContract of SubmitReview as shown below: 

    [ServiceContract]
    public interface IProductService
    {
        [OperationContract(IsOneWay=true)]
        void SubmitReview (ProductReview pr);

    }

8. Add the endpoint for MSMQ

<endpoint address="net.msmq://localhost/private/productservice" binding="netMsmqBinding"
bindingConfiguration="NetMsmqBindingConfig" contract="ProductServiceLibrary.IProductService" />


9. Add binding configuration for the above endpoint
       <bindings>
        <netMsmqBinding>
          <binding name="NetMsmqBindingConfig" exactlyOnce="false">
            <security mode="None"></security>
          </binding>
        </netMsmqBinding>

        </bindings>

10. Test the console host. It should work without any issues.

11. Update the service reference in the client.

ProductServiceClient client = new ProductServiceClient("NetMsmqBinding_IProductService");

12. Run the Service Host and Client at the same time and test it.

13. Now run only the service client and notice that it accepts a new product review even when the host is not running.

14. Go the Computer Management and check the ProductReview Queue you notice that there is a message that has been queued.

15 Try submitting another product review using the client, now you should see two messages queued

16. Now run the service host. Notice that service host now shows that two reviews have been added.

17. Check the productReview queue in the computer management you will not see any message queued now.

Comments

Popular posts from this blog

CUMIPMT and CUMPRINC function

CUMIPMT Cumulative interest payment function allows you to calculate the interest paid for a loan or from an investment from period A to period B. When getting a loan, CUMIPMT function can be used to calculate the total amount of interest paid in the first five months or from period 12 to period 20. A period can be a month, a week or two week. Loan Amount : 350,000.00 APR: 4.5% Down payment: 0.00 Years: 25 Payment per year: 12 From the above data, we can calculate the following: No of Period: 25 × 12 = 300 Periodic Rate: 4.5/12 = 0.375% Here is how you will substitute these values into the function. = CUMIPMT (periodic rate, No of period, vehicle price, start period, end period,  ) = CUMIPMT (0.375, 300, 350000, 1, 5, 0) In an excel worksheet, we use cell address instead of actual values as shown below: Here is the formula view of the worksheet: CUMPRINC Another related function is CUMPRINC. CUMPRINC function is used to calculate cumul

Excel PMT Function

PMT function is very useful for calculating monthly payment required to payback a loan or mortgage at a fixed rate. This function require a minimum of three inputs, periodic rate, number of periods, present value or the loan amount. Here is a simple example. Home Loan: 350,000.00 Interest rate: 4.5% Number of years to repay the loan: 25 Note: To calculate monthly payment, we need to find the monthly rate and number of months as shown above. Then it is simply a matter of substituting the values into the payment function, as shown in the formula view below.

BCG's Brand Advocacy Index

The Boston Consulting Group's (BCG) Brand Advocacy Index (BAI) is a metric developed to help companies measure the degree of customer advocacy for their brands. BAI focuses on the likelihood of customers to recommend a brand to others, which is a powerful indicator of brand strength and customer loyalty. Unlike other customer satisfaction or loyalty metrics, BAI emphasizes the importance of customer referrals and word-of-mouth marketing. BAI is calculated based on a survey where customers are asked about their willingness to recommend a brand to their friends, family, or colleagues. The responses are then used to compute a score, which ranges from -100 to 100. A higher BAI score indicates that a brand has more advocates who are likely to recommend the brand to others, while a lower score suggests that the brand has fewer advocates or even a higher number of detractors. BCG's research has shown that companies with higher BAI scores tend to experience higher growth rates and bett