No more typing reviews! Try our Samantha, our new voice AI agent.

IBM WebSphere Message Broker vs Microsoft .NET Framework comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM WebSphere Message Broker
Ranking in Application Infrastructure
17th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
13
Ranking in other categories
Enterprise Service Bus (ESB) (9th)
Microsoft .NET Framework
Ranking in Application Infrastructure
2nd
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
57
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Application Infrastructure category, the mindshare of IBM WebSphere Message Broker is 2.7%, up from 1.6% compared to the previous year. The mindshare of Microsoft .NET Framework is 4.1%, down from 6.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Infrastructure Mindshare Distribution
ProductMindshare (%)
Microsoft .NET Framework4.1%
IBM WebSphere Message Broker2.7%
Other93.2%
Application Infrastructure
 

Featured Reviews

MANUEL VALDIVIA - PeerSpot reviewer
Senior Manager at a financial services firm with 1,001-5,000 employees
Routes messages efficiently across our services, but the features for scalability need improvement
One of the key benefits has been its ability to expose services and securely integrate applications within our architecture. It's been integral in maintaining a stable infrastructure despite its limitations with dynamic service creation and flexibility compared to newer technologies like Kubernetes. The main challenge has been scalability during peak usage times.
Muhammad Qasim - PeerSpot reviewer
Solutions Architect at Diyar United Company
Has enabled building responsive multi-threaded applications while supporting rapid deployment workflows
Microsoft .NET Framework has already made significant improvements by becoming open source. Many developers are contributing to Microsoft .NET Framework, not just Microsoft itself. They have ported it to many platforms and allow a healthy ecosystem of open source tools. They have moved from Visual SourceSafe to supporting Git with Microsoft Visual Studio. Their IDE, Visual Studio Code, is open source and multi-platform. There are many third-party tools available, including AI-based tools such as Cursor and Bolt, which are forks of Visual Studio Code. Based on my understanding, I don't have any suggestions for improvement as they are already doing an excellent job.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Straightforward development and deployment."
"The solution has good integration."
"We only use the basic features, but the most valuable one for us is the Publish-subscribe pattern."
"IBM WebSphere Message Broker is one of the best middleware solutions"
"Message Broker is valuable because most of the applications are using MQ. Even in my current engagement, the few applications which I audit to onboard the bank are using MQ."
"The documentation, performance, stability and scalability of the tool are valuable."
"The transactions and message queuing are the most valuable features of the solution."
"Performance-wise, this solution is really good."
"Basically, .NET is simply is the easiest programming language to use, based on my experience."
"As we are scaling quite nicely on Azure."
"The new .NET Core has those middlewares, which are awesome from a security standpoint. With the old Framework or the newer Framework, middleware is basically an event pipeline. You configure and register it, and it handles things centrally. A simple example is logging. With the old Framework, you needed to try/catch blocks everywhere. Here, you configure the logging handler once, and it captures exceptions across the application. I really like the middleware pattern."
"I'd rate the solution as highly stable."
"The Windows Communication Foundation is the biggest advantage we get from the .NET Framework."
"The .NET Framework simplified operations dealing with the allocation and deallocation of memory spaces and the additional processing resources."
"The solution is not limited in storage, is customizable and simple to use."
"Whenever someone needs a very good back-end system or a strong system, they should go with C# .NET technologies."
 

Cons

"My biggest complaint about this product is the price."
"As our business requirements evolve, we require more dynamic capabilities to adapt and scale our services accordingly."
"They are expensive and not worth the money we are spending on them."
"Technical support is very slow and needs to be improved."
"The solution can add container engines such as docker."
"The images and size of the containers are too big and I think that they should be more lightweight."
"Technical support is good but they could have a better response time."
"I find the installation configuration is quite difficult compared to other solutions."
"The integration with DevOps tools, such as Azure DevOps, Jira, and GitLab, would be a valuable addition."
"The price of the Enterprise version is quite high and can be improved."
"Improvements are needed in .NET development, particularly in a backend scenario."
"The solution could improve by optimizing the memory for better performance."
"I would want the product to be integrated with the different AI tools in the future since it is one of the areas where the product has certain shortcomings."
"The solution needs to update its security periodically because there are many security concerns."
"The solution has difficulty integrating with other products. There are no such difficulties if you have the same platform, hardware, and operating system."
"In the realm of Microsoft .NET Framework, particularly in the C# language, there have been significant developments that I find highly commendable. I am genuinely fascinated by the continuous evolution of the language, and staying abreast of the latest features in Azure is both challenging and enjoyable. Working with C# in Azure is particularly fantastic. I appreciate in .NET, as compared to Java, is the enforcement of types, providing a better experience in terms of technicalities. Additionally, the introduction of Roslyn in the past few years has brought about the concept of late .NET, which I find interesting and powerful. This allows for the transformation of symbolic code just before execution, eliminating the runtime decision-making process and enhancing efficiency. However, late .NET does come with a drawback – a delay in the last-minute computation when starting an executable. While some may find this less appealing in terms of instant responsiveness, especially in serverless cloud environments, the efficiency gained from executing strictly binary code is valuable. Despite potential drawbacks like the time required for activation, I view .NET favorably for its technical advancements and efficiency, especially in scenarios such as serverless cloud computing. It's essential to recognize the intricacies of how .NET processes code and the efficiency it brings, which some may overlook."
 

Pricing and Cost Advice

"IBM software can be costly, but having a contract has helped manage and potentially lower costs over time."
"This product is more expensive than competing products."
"The solution is expensive."
"The licensing cost of IBM WebSphere Message Broker needs to be reduced"
"The solution is expensive."
"The price is very high and it's the main reason that we are searching for alternatives."
"IBM products are generally more stable and have more features, but also come at a greater cost."
"I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons. There are always additional fees."
"Microsoft .NET Framework is a free, open-source solution."
"The product’s pricing is a bit high."
"If you want to develop an enterprise-level application, you have to purchase the enterprise-level development license."
"The product and support for this solution are free for everyone."
"Considering the bigger picture, opting for the Microsoft ecosystem can be beneficial and it is priced well. When relying on entirely open-source solutions, you may encounter challenges associated with dealing with multiple vendors and potentially compromised security measures. However, it is important to note that Microsoft could enhance its performance when it comes to addressing critical security concerns."
"The solution is free but you need to pay for a license for the hosting service."
"The support is an extra cost when purchasing the license. The price of the solution is overall reasonable and paid annually or every three years. Additionally, they have a monthly license. The cost is approximately $1,000 per user."
"Do your homework. Consider the partnership program."
report
Use our free recommendation engine to learn which Application Infrastructure solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Construction Company
13%
Manufacturing Company
10%
Computer Software Company
7%
Construction Company
19%
Financial Services Firm
11%
Real Estate/Law Firm
10%
Outsourcing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Large Enterprise10
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise10
Large Enterprise23
 

Questions from the Community

What is your experience regarding pricing and costs for IBM WebSphere Message Broker?
IBM software can be costly, but having a contract has helped manage and potentially lower costs over time.
What needs improvement with IBM WebSphere Message Broker?
There could be greater flexibility and agility in service creation for the product. As our business requirements evolve, we require more dynamic capabilities to adapt and scale our services accordi...
What is your primary use case for IBM WebSphere Message Broker?
We use the product for exposing services at the application level, integrating with various architectures like WebSphere, and handling static service creation.
What is your experience regarding pricing and costs for Microsoft .NET Framework?
I don't know about pricing. I'm paying for Visual Studio, even though I'm not using the new version yet. Prices can always be better, but I think for the environment provided, the prices are accept...
What needs improvement with Microsoft .NET Framework?
The Visual Studio ID that we are using requires more RAM and IP. Sometimes it goes high on this phone exchange, and it crashes sometimes. We have to review this with Microsoft itself. That is somet...
What is your primary use case for Microsoft .NET Framework?
We have been using the Viasat QoS, which is a web application platform. We are using a part of this web application. Regarding Nexity, we are not getting whatever they are offering, but it is fine ...
 

Also Known As

WebSphere Message Broker
MS .NET Framework
 

Overview

 

Sample Customers

WestJet, Blue Cross and Blue Shield of North Carolina, Sharp Corporation, Michelin Tire
Curtin University, Rockwell Automation, Aruba Networks, Insurity Inc., City of Barcelona, Pennsylvania DCNR, University of Petroleum and Energy Studies, A1 Telekom Austria AG, Eastman Chemical Company
Find out what your peers are saying about IBM WebSphere Message Broker vs. Microsoft .NET Framework and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.