We performed a comparison between IBM DataPower Gateway 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."The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"It's high-speed and it can be remotely administered via an API."
"The MPGW (Multi-Protocol Gateway) is great because it allows you to easily expose services using various protocols – web services, REST (JSON), and others. This flexibility simplifies things."
"What I like most is the stability."
"The performance is good. It's been very stable."
"The most valuable feature is the security appliance, it's very secure."
"The API Connect gateway service and the SQL injection feature is good."
"The solution is robust."
"When we talk about .NET development, we use Visual Studio IDE to create these things. In recent years, there have been a lot of improvements in Visual Studio 2022. It would be a daunting task to list all of the features that have benefited us, as it would require a lot of time and effort. However, there are definitely many improvements year after year in .NET development."
"When it comes to the user interface, the context is better than other tools because it is easier to use."
"Given that it's cross-platform right now, where you can use it on Windows and Mac, that is the single most significant feature that has resulted in wider adoption of .NET."
"The most valuable thing about Microsoft .NET Framework is that it is an enterprise-grade language and platform."
"In my opinion, the best thing about Microsoft .NET is the fully featured framework. It provides most of the things which a normal developer requires of any application out of the box."
"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."
"It is a stable solution."
"The solution is easy to use if the user is a developer or some technical person."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"It is a costly product."
"Traceability could be improved, especially for business operations. The traceability of the transactions could be an improvement point for DataPower to work on. It would be better if they provided JSON support. JSON protocol data has changed format. It started performing internal transformation to JSONx. This might be an additional complexity."
"Scripting needs improvement. It's hard for our customers."
"DataPower isn't the most user-friendly tool. It is not an easy tool to use. Some things could use better wizards to guide you through processes."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"The solution is difficult to learn if someone is learning it for the first time."
"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."
"The solution could improve by optimizing the memory for better performance."
"They should have more training materials available that are specific to .NET. We spend a lot of money training our engineers."
"The product is nearing its sunset, and we think that by 2028, we won't get support anymore"
"You need to have the technical expertise to use this product."
"The pricing is a bit expensive."
"Improvements are needed in .NET development, particularly in a backend scenario."
IBM DataPower Gateway is ranked 6th in Application Infrastructure with 27 reviews while Microsoft .NET Framework is ranked 4th in Application Infrastructure with 47 reviews. IBM DataPower Gateway is rated 8.4, while Microsoft .NET Framework is rated 8.4. The top reviewer of IBM DataPower Gateway writes "Security features meets compliance needs and offers MPGW (Multi-Protocol Gateway) that simplifies integration efforts ". 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 DataPower Gateway is most compared with IBM API Connect, Apigee, Microsoft Azure API Management, Mule ESB and IBM Integration Bus, whereas Microsoft .NET Framework is most compared with IIS, Magic xpa Application Platform, JBoss Enterprise Application Platform, Apache Web Server and Oracle WebCenter. See our IBM DataPower Gateway 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.
