WebSphere DataPower Gateway is really beneficial if you are trying to integrate two or more systems. It provides you with comfort and peace of mind by creating a DMZ zone for the services which are going out of the intranet to hit external clients APIs. It is greatly recommended if you have a very high volume service or API which is being used by a majority of clients because it has a dedicated physical box present which takes care of memory, CPU and all such stuff. So, all your transactions happen at wire-speed.
.NET is well suited for any general purpose solution to a business problem, though if we are talking strictly the framework version - you have to be more or less tied to Microsoft Windows to run it. If this isn't a problem, then it will be able to address and solve any programming project you have.
The most obvious thing that DataPower does exceptionally well is security. All the built-in supported security capabilities allow us to isolate most security tasks to DataPower and as a result "protect" down steam services/systems to have to deal with security.
DataPower is very good at protocol conversion and as it is usually used on the edge allows you to narrow down the protocols used between the companies public and private networks.
The appliance concept makes maintenance, recovery and, management so much simpler.
The old interface is being really missed by our team as the new WebUI interface is not that intuitive or easy to work with. It takes a lot of time to load. There should be an inbuilt wizard for creating a Rest service as well like there is for an XML based service.
IBM support is very knowledgeable but it's not that easy to reach them. They don't release the fix patches very soon which also becomes a big issue in certain situations where critical projects are involved.
Lastly, DataPower has its steep learning curve and it requires time and effort on your end to gain full control and make the most of the advanced features which it offers. Finding the right resource in the market is not that easy.
.NET is heavily Microsoft Windows oriented, and while .NET core tried to resolve that with MacOS and Linux support, .NET Core is still waiting for wider adoption.
While free for small projects, additional features for big projects can be a little expensive.
Can be resource-heavy upon deployment. We continuously have our more senior staff optimize the code of our junior developers for performance. Other languages are a little bit more forgiving in comparison.
The full .NET Framework is an amazing thing and is very robust. We have used it to create console apps, Windows apps, and online apps. When coupled with Visual Studio, development, testing, building, and deploying our applications has become 100 times easier as compared to doing those things manually before. The automation of this process has helped us push out changes to our applications faster to adapt to the ever-changing business requirements.
You don't often need to reach out to Microsoft for .NET support. If you do, there are forums and websites that have active Microsoft support folks where you can provide feedback or get help. Microsoft support in general is quite good as well, but not cheap. The best support is from the community like StackOverflow.
The .NET platform has a much longer and broader history than Laravel, so we chose to go with it as the support will be far superior. Additionally, Laravel is tied to PHP, while you can use multiple different languages in .NET. The additional flexibility that .NET provides in the range of types of applications you can build with it sealed the deal.
It has really taken our business to the next level. We have expanded and integrated with so many new vendors and for all those integrations DataPower is serving as our security gateway.
We don't have to depend on any other tool for doing the load balancing of the incoming requests as that is also taken care inside the WebSphere DataPower Gateway box itself, thereby distributing the load equally.
It has made our platform much more secure, uniform and robust to deal with any kind of incoming message format or threat as well due to its latest security mechanisms and huge processing power.
There are few factors we needed for our custom development. Below are each of them. We were able to get a satisfactory outcome for each of these factors which made .NET platform a very good choice in developing enterprise applications.
Reusability of codes- Microsoft has given many re-usable codes and components in the framework to help developers do their job effortlessly. With the help of default features, developers can create end-to-end solutions and make the business operations more efficient. As codes and components are reusable, .NET reduces development time and if applications take less time to develop, they cost cheaper and you get faster return on investment.
Easy to maintain- Development cost is one time, but maintenance cost is incurring. .NET apps are easily maintainable, thanks to the configuration settings that can be modified without any need to rewrite the code.
Deployment is hassle free- Deploying software is always challenging and the most common problem developers face in this process is the existence of multiple DLLs. It’s hard to make sure that all DLLs will co-exist in the same machine. .NET framework solves this problem by allowing different versions of the same DLL to exist side-by-side on the same machine.
Security- .NET is one of the most secure web and application development frameworks available in the market. As it’s made by Microsoft, you can be absolutely sure about the security measurements. Hackers can never steal valuable data from your website or apps.
Cross platform friendly- What if you had developed an app for desktop and laptop computers and now after seeing the growth of mobile apps in the market, you want it in mobile version as well? You can easily develop an app that runs on the desktop and PDA without any issue. As you can re-use the codes and utilize the same development environment, your job becomes a lot simpler.
