IBM InfoSphere Information Server vs. Mule ESB

Information Server is extremely useful to replace manual developments that require a lot of coding effort. It significantly increases the productivity of the initial development and the future maintenance of the processes since it has a visual development environment with self-documentation.

If you’re bringing anything into Salesforce you should just invest now into Mule, you will get your money’s worth and find a myriad of uses to build APIs between many other systems. Once you build a component you can easily reuse it as a building block to attach to another source/destination. This makes it easy to ramp up quickly and spread usage of Mule throughout your enterprise. A good value for medium to large companies, but probably cheaper to outsource your job to a consulting firm if you are smaller.

Incentivized

• IIS best for ETL ,not ELT , and many and diffrent source systems.
• It also can process big data , unstuctured data
• It is not only DWH , you can use infosphere for analys and see the bigger architecture of your OLTP systems

Incentivized

• It is best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
• Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
• Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
• Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.

Incentivized

• I would be nice to have a new web development environment for DataStage.
• Connectivity Packs such as Pack for SAP Application are a little pricey.
• It is confusing for new developers the possibility of developing jobs using different execution engines such as Parallel or Server.

Incentivized

• Make sure to not over-engineer shared components. It can complicate development
• Create a roadmap for where you are going - if not, you may miss components
• I suggest getting support, otherwise it could be a difficult learning curve

Incentivized

• Scale of implementation
• IBM techsupport

Incentivized

DataStage is more robust and stable than ODI The ability to perform complex transformations or implement business rules is much more developed in DS

It doesn't have API . We have to go for another API manager. But in Mule, it has both API manager and ESB

Incentivized

• Productivity of the development of integration processes.
• Better documentation and governance.
• Reduce training costs of various technologies.

• Overall a great tool for complex integrations

Incentivized