We performed a comparison between IBM BPM 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 case management and its integration with process design are good features."
"It is a stale solution."
"Setting it up is fairly easy. If somebody has knowledge of the system, he or she will be able to do it fairly quickly."
"Agility is the key. It gives our customers a faster way to be able to implement processes, get ownership of task, visibility into a process. The ability to modify that process, optimize that process over time, is probably the biggest benefit that they get from the software."
"It continues to keep up with the changing needs of the business. That is the strong value proposition of BPM. It's not a one-time automation."
"The possibility to add Java code as embedded .jar, that increases the flexibility of the solution."
"It has improved my organization quite a bit. It brought awareness to what the business processes are, even to the business side, who did not necessarily know what they are."
"Compliance with the BPMN 2.0 standard."
"The most valuable feature is customization."
"The tool offers a lot of support, and there is a lot of knowledge material available, along with a lot of community groups."
"The solution is easy to use if the user is a developer or some technical person."
"Firstly, I appreciate the decision to use Microsoft .NET Framework. I find it to be an excellent language, with a history rooted in providing an alternative to Java, albeit with initial challenges. It is gaining popularity and may be voted the most desirable programming language. What I particularly like about .NET is its language efficiency. While C# is the primary language, the platform also supports others, catering to those inclined towards functional programming. Although I started with Shell, I'm still grasping the concept of functional programming. Despite initial reservations about object-oriented programming, I acknowledge its advantages. .NET is a safer option, and despite criticisms, it has evolved over the years. One notable aspect is .NET's transition to an open platform in recent years, distancing itself from being exclusive to Microsoft engineers. I appreciate the versatility of .NET, enabling code production for a wide range of platforms, presenting a strong competition to Java. It allows targeting practically any physical platform, showcasing its flexibility. These qualities contribute to my positive view of .NET, totaling thirteen aspects that I find appealing."
"The product has a good interface and easy-to-use programming language."
"Microsoft .NET Framework reduces the cost of entry and enables the development of applications with mature and enterprise features, thereby lowering the entry barriers."
"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."
"As we are a software company, we find that accessing resources using this technology is easier compared to the others."
"You must have good experience to work with it. It is not that easy. Its installation is complex, especially in the new version for business automation, and it could be improved. It has a safety application embedded inside it, and you need to do a lot of configuration to install it. I have been working for two days to resolve an issue."
"There needs to be better documentation for IBM BPM in a central place. There is not any standard documentation for each component available and has been a barrier for developers."
"The initial setup was complex."
"I hope IBM uses something from IBM Content Navigator to make the interface easier to navigate."
"Performance in the development environment space. I know that they have been taking it off the desktop version and putting on the web, and it is not 100% yet."
"The tool's workflow function is very strong."
"There is a lot of room for improvement of the dashboards."
"They don't have a mechanism to achieve processes, data sources, and data."
"The product could have a better framework for application development."
"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."
"There are performance constraints when multiple users are accessing the application and that consumes CPU resources."
"They should try to improve their Blazor WebAssembly."
"One thing that could be improved is the tooling and IDE for .NET in non-Windows environments like Mac."
"The product is nearing its sunset, and we think that by 2028, we won't get support anymore"
"The learning curve could be improved."
"Better integration with other tools to make the operation faster would be an improvement."
IBM BPM is ranked 7th in Application Infrastructure with 105 reviews while Microsoft .NET Framework is ranked 4th in Application Infrastructure with 47 reviews. IBM BPM is rated 7.8, while Microsoft .NET Framework is rated 8.4. The top reviewer of IBM BPM writes "Offers good case management and its integration with process design but there's a learning curve". 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 BPM is most compared with Camunda, Appian, Pega BPM, IBM Business Automation Workflow and Apache Airflow, whereas Microsoft .NET Framework is most compared with IIS, Magic xpa Application Platform, JBoss Enterprise Application Platform, Apache Web Server and SAP NetWeaver Enterprise Portal. See our IBM BPM 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.