IBM WebSphere Message Broker vs Microsoft .NET Framework comparison

Cancel
You must select at least 2 products to compare!
IBM Logo
586 views|505 comparisons
90% willing to recommend
Microsoft Logo
3,259 views|2,009 comparisons
93% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between IBM WebSphere Message Broker and Microsoft .NET Framework based on real PeerSpot user reviews.

Find out in this report how the two Application Infrastructure solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed IBM WebSphere Message Broker vs. Microsoft .NET Framework Report (Updated: March 2024).
768,246 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"It has many interfaces and you can connect to any backend source that has another format, and convert it to the desired format.""It is a scalable solution...The setup is easy.""The transactions and message queuing are the most valuable features of the solution.""The solution has good integration.""Integration and mapping are easy, which is a major advantage.""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.""We only use the basic features, but the most valuable one for us is the Publish-subscribe pattern.""The documentation, performance, stability and scalability of the tool are valuable."

More IBM WebSphere Message Broker Pros →

"The most valuable feature is customization.""A great solution for creating program solutions in a framework for Microsoft Windows quickly and easily.""In-built refactoring and .Net profilers are the most valuable features of the solution.""I'd rate the solution as highly stable.""Initial setup is straightforward. All the components are readily available.""The addition of generics to handle common functionality across types, and the more recent upgrade of the dataset to the Entity Framework, has cut development time drastically, while increasing quality and confidence between builds.""Proven solution with valuable customization.""Microsoft .NET Framework continually innovates, particularly in Visual Studio, which focuses on improving languages, debugging, and .NET functionality."

More Microsoft .NET Framework Pros →

Cons
"It is currently a weighty product.""There is some lag in the GUI. There have been some performance issues and maybe it's because of the application data.""The installation configuration is quite difficult.""The images and size of the containers are too big and I think that they should be more lightweight.""Stability and pricing are areas with shortcomings that need improvement.""Technical support is good but they could have a better response time.""Today I probably wouldn't go for Message Broker because of the cost structure, support, and the whole ecosystem around IBM.""I know that Message Broker was a very tightly copied product with another IBM product, that is, IBM MQ. I would like to have a little bit more decoupling from the IBM MQ because it should not be a prerequisite for IBM WebSphere Message Broker usage."

More IBM WebSphere Message Broker Cons →

"The solution has difficulty integrating with other products. There are no such difficulties if you have the same platform, hardware, and operating system."".NET Is still heavy or dependant on other Microsoft libraries and frameworks.""The .NET open source community could be larger.""They should try to improve their Blazor WebAssembly.""It is of great concern to us that the solution is not very powerful on cross platform, at it impedes the ability to build and scale with it.""Microsoft has its own product called Blazor, but I don't think it's quite as powerful yet as React or Angular. That's an area for improvement.""I would like more web integration.""There are performance constraints when multiple users are accessing the application and that consumes CPU resources."

More Microsoft .NET Framework Cons →

Pricing and Cost Advice
  • "IBM products are generally more stable and have more features, but also come at a greater cost."
  • "The price is very high and it's the main reason that we are searching for alternatives."
  • "This product is more expensive than competing products."
  • "I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons. There are always additional fees."
  • "The solution is expensive."
  • "The solution is expensive."
  • More IBM WebSphere Message Broker Pricing and Cost Advice →

  • "Do your homework. Consider the partnership program."
  • "The product and support for this solution are free for everyone."
  • "The pricing could be cheaper."
  • "There is a Community Edition that can be used free of charge, but the licensing cost for the Enterprise version is quite high."
  • "If you want to develop an enterprise-level application, you have to purchase the enterprise-level development license."
  • "The Microsoft .NET Framework is free of charge, without licensing cost."
  • "For the moment I can only give the product a rating of five out of ten since only some of the customers will be satisfied, those that have the financial resources for hosting a platform on Windows Server."
  • "Microsoft .NET Framework is licensed under the Windows License."
  • More Microsoft .NET Framework Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Application Infrastructure solutions are best for your needs.
    768,246 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:It is a scalable solution...The setup is easy.
    Top Answer:The solution is expensive. I give the cost a one out of ten. We pay for an annual license.
    Top Answer:Stability and pricing are areas with shortcomings that need improvement.
    Top Answer:Microsoft .NET Framework continually innovates, particularly in Visual Studio, which focuses on improving languages, debugging, and .NET functionality.
    Top Answer:Microsoft .NET Framework continually innovates, particularly in Visual Studio, which focuses on improving languages, debugging, and .NET functionality. They could enhance support for Python within… more »
    Ranking
    Views
    586
    Comparisons
    505
    Reviews
    5
    Average Words per Review
    384
    Rating
    8.4
    Views
    3,259
    Comparisons
    2,009
    Reviews
    27
    Average Words per Review
    469
    Rating
    8.3
    Comparisons
    Also Known As
    WebSphere Message Broker
    MS .NET Framework
    Learn More
    Overview
    WebSphere Message Broker is an enterprise service bus (ESB) providing connectivity and universal data transformation for service-oriented architecture (SOA) and non-SOA environments. It allows businesses of any size to eliminate point-to-point connections and batch processing regardless of platform, protocol or data format.

    Microsoft .NET Framework is a software development framework for building and running applications for Windows, Windows Phone, Windows servers, XML Web services, and Microsoft Azure. The software is made up of two major components: Common Language Runtime (CLR) and the .NET Framework Class Library. The CLR is the execution engine that handles running apps and the Class Library is a library of tested, reusable code that developers can call from their own apps.

    Microsoft .NET Framework Features

    Microsoft .NET Framework has many valuable key features. Some of the most useful ones include:

    • Memory management: With Microsoft .NET Framework apps, the CLR allocates and releases memory and handles object lifetimes in many programming languages, so programmers are not responsible to do it.
    • Multitargeting: Microsoft .NET Framework targets .NET Standard, allowing developers to create class libraries that work on multiple Microsoft .NET Framework platforms.
    • A common type system: When using Microsoft .NET Framework, basic types are defined by the .NET Framework type system and are common to all languages that target Microsoft .NET Framework as opposed to traditional programming languages where basic types are defined by the compiler.
    • Side-by-side execution: By allowing multiple versions of the common language runtime to exist on the same computer, Microsoft .NET Framework helps resolve version conflicts. In addition, an app can run on the version of Microsoft .NET Framework with which it was built and multiple versions of apps can coexist.
    • Development frameworks and technologies: Microsoft .NET Framework provides libraries for specific areas of app development, such as ASP.NET for web apps, ADO.NET for data access, Windows Communication Foundation for service-oriented apps, and Windows Presentation Foundation for Windows desktop apps.

    Microsoft .NET Framework Benefits

    There are many benefits to implementing Microsoft .NET Framework. Some of the biggest advantages the solution offers include:

    • Language interoperability: With this Microsoft .NET Framework feature, routines written in one language are accessible to other languages, enabling programmers to focus on creating apps in their preferred languages.
    • Version compatibility: Microsoft .NET Framework offers version compatibility for rare occasions when apps that are developed by using a particular version of Microsoft .NET Framework happen to run without modification on a later version.
    • Extensive class library: With Microsoft .NET Framework, programmers have the ability to use a readily accessible Microsoft .NET Framework class library instead of having to write vast amounts of code to handle common low-level programming operations.

    Reviews from Real Users

    Below are some reviews and helpful feedback written by PeerSpot users currently using the Microsoft .NET Framework solution.

    PeerSpot user, Syed A., Principal System Developer at a government, says the solution is a “Great all in one framework with extensive stack for web applications, windows applications and mobile applications.”

    A QA Supervisor at a manufacturing company mentions, “It comes with many features that you can interact with and has all of the libraries readily available, which is not available in the RPA platforms. You can create your own SSIS package. You can integrate with all of the Windows objects, which is not available in Automation Anywhere, and you need to rely on their Object Cloning technologies to interact with them.”

    Brennan G., IS Technical Architect at Avara Foods Holdings Limited, comments, “It is easy to use, and it runs on a Windows platform. The .NET Framework is a very good framework. It does what I need it to do.”

    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
    Top Industries
    VISITORS READING REVIEWS
    Financial Services Firm27%
    Computer Software Company12%
    Insurance Company9%
    Retailer6%
    REVIEWERS
    Government19%
    Manufacturing Company15%
    Computer Software Company11%
    University11%
    VISITORS READING REVIEWS
    Computer Software Company14%
    Financial Services Firm13%
    Government9%
    Manufacturing Company7%
    Company Size
    REVIEWERS
    Small Business18%
    Large Enterprise82%
    VISITORS READING REVIEWS
    Small Business16%
    Midsize Enterprise11%
    Large Enterprise74%
    REVIEWERS
    Small Business50%
    Midsize Enterprise13%
    Large Enterprise37%
    VISITORS READING REVIEWS
    Small Business23%
    Midsize Enterprise14%
    Large Enterprise63%
    Buyer's Guide
    IBM WebSphere Message Broker vs. Microsoft .NET Framework
    March 2024
    Find out what your peers are saying about IBM WebSphere Message Broker vs. Microsoft .NET Framework and other solutions. Updated: March 2024.
    768,246 professionals have used our research since 2012.

    IBM WebSphere Message Broker is ranked 10th in Application Infrastructure with 11 reviews while Microsoft .NET Framework is ranked 4th in Application Infrastructure with 47 reviews. IBM WebSphere Message Broker is rated 7.8, while Microsoft .NET Framework is rated 8.4. The top reviewer of IBM WebSphere Message Broker writes "For new applications that are being onboarded, we engage this tool so the data can flow as required but there's some lag in the GUI". On the other hand, the top reviewer of Microsoft .NET Framework writes "Intuitive, easier to develop, maintain, and migrate from the old framework to newer versions". IBM WebSphere Message Broker is most compared with IBM Integration Bus, webMethods Integration Server, Mule ESB, IBM DataPower Gateway and IBM BPM, whereas Microsoft .NET Framework is most compared with IIS, Magic xpa Application Platform, Apache Web Server, JBoss Enterprise Application Platform and Windows Process Activation Services. See our IBM WebSphere Message Broker vs. Microsoft .NET Framework report.

    See our list of best Application Infrastructure vendors.

    We monitor all Application Infrastructure reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.