Microsoft IIS is an application server and infrastructure.
N/A
WSO2 Enterprise Service Bus
Score 7.1 out of 10
Enterprise companies (1,001+ employees)
WSO2 says they have taken a fresh look at old-style,
centralized ESB architectures, and designed their unique WSO2 Enterprise Service Bus
from the ground up as the highest performance, lowest footprint, and most
interoperable service oriented architecture (SOA) and integration middleware
today. Additionally, the vendor says that by relying on their carbon technology
the ESB is able to deliver a smooth start-to-finish project experience.
N/A
Pricing
Microsoft IIS
WSO2 Enterprise Service Bus
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Microsoft IIS
WSO2 Enterprise Service Bus
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft IIS
WSO2 Enterprise Service Bus
Features
Microsoft IIS
WSO2 Enterprise Service Bus
Application Servers
Comparison of Application Servers features of Product A and Product B
Publishing applications or websites is easy with Microsoft IIS. You don't need external software or complicated tutorials involving command lines and editing configuration files. On other hand, sometimes the troubleshooter needs a high knowledge of Windows Server, Registry, and tools to debug the application. If you need to host non-Microsoft technology as PHP pages or have a low budget, I recommend IIS equivalent software as Apache.
WSO2 ESB is an awesome product for companies looking to venture into the world of SOA with an ESB. They have a lot of other products too that can work really well with their carbon infrastructure. The interface is simple for deploying and managing proxy services. You can also write custom modules within the ESB using Java with IDE like Eclipse
A big advantage that we use all the time is reviewing the logs that automatically get generated in IIS. It has helped us troubleshoot various problems in our applications over the years.
IIS integrates really well with Visual Studio and TFS. We are able to quickly deploy new applications and changes to applications when requested by the business.
IIS has proven that it is easy to configure and maintain with minimal effort.
One of the basic requirement of an ESB product is that it should be able to support transformation. WSO2 ESB provides support of XSLT, so you can transform your request to whatever format. Moreover, transformations like converting your xml payload into JSON and JSON payload to XML are out of the box available.
WSO2 ESB provides a scheduler feature, by which you can configure your own scheduler to call a proxy service at a particular time of day or or initiate sequence.
WSO2 ESB provides excellent error handling techniques, WSO2 ESB provides detailed error handling scenarios to tackle all the situations. WSO2 ESB also provides custom error handling by which you can make your own custom error message before sending it back to client.
We have no intention to replace all applications running on top of the IIS platform. Not all applications support other platforms and not all support staff are skilled in Linux/Apache platform support. Whereas IIS may not be the best performing or most secure web platform available, for the aforementioned reasons, it is impossible not to continue use of this product.
As I've mentioned earlier, Microsoft IIS is very simple and easy to use. The user interface is a little bit overloaded with a huge number of different options, but once you have a little clue of what you are doing and what you need - no issues at all.
ARR (application request routing) in Microsoft IIS Server enables the web-admins to increase the web app reliability and availability through the rule based routing and load balancing of HTTP requests which in turn provides highly available server. IIS 7.0 Manager also provides kernel as well as user mode caching for faster performance and in case if the server fails, the IIS server has good amount of details logged in its log files which help understand and debug the cause quickly. Load balancing facilitates IIS server to fight against availability issues.
Lack of auto-restart built-in capabilities. In case of running out of memory there are no built-in methods to recover from a crash, just for example, Oracle WebLogic Node Manager.
In my experience, I have never had significant issues with IIS performance. Sometimes I've experienced issues with loading time, but it is mostly related to the web site code. However Amazon, Microsoft and Google providing free cloud services with very limited resources, and in that scenario, "heavy" websites on IIS could be the issue. In other situations - performance is good.
As mentioned earlier there is so much documentation or guides or stack overflow questions out there that someone will have faced the same or very similar scenario to what you are going through that you will almost certainly find a solution to what you are after.
Apache is java. Java is unnecessary complex. No developer wants to invest in learning all the hundreds of text based configuration files to get something done. Also, apache gives you the most evil and un-usable user interface possible. [Microsoft] IIS makes [life] after development easy, which is already complex enough to be bothered by something as mundane as exposing your work over the internet.
Microsoft IIS Server is scalable if the underlying server configuration is done correctly. Use x64 edition v/s 32bit and using 32bit mode application pools are some of the tweaks to be done to make the IIS server scalable. There are too many small configurations need to be carried out in order to make a highly scalable IIS server hence not giving full score in this area.
