Surendranath C

This can be split into two aspects - Features and Functionality - Quality of Service - Industry support Within the first, we would evaluate on: - Support for different Operating System Platforms - Availability of API across languages, in order of importance - Java, C#,…

ESB's have transformed from being point solutions into truly multi-purpose applications. ESB from traditional sources of integration technologies - Tibco and from the IBM Websphere family - will rule the roost in large enterprises Mule is a close follower from the JBoss…

Orlee The primary use cases have been - REST API to extract data in JSON format - Custom logic for interpretation of data - Transformation of interpreted/derived data into Java objects - Java --> JSON transformation and another REST call to load it to a target In each…

We used the HTTP Connector and also re-used a custom connector built for a 3rd party product. The REST API to integrate with the 3rd party product was abstracted away for us For one Mule flow, we needed to integrate with the enterprise security module. This was made easy…

Mule as an ESB has something for everyone. Wide range of connectors and being built on top of the Spring framework are definite advantages in picking up the product

Pre-built data masking components. I built it exclusively as a pure Java 7 solution. I even avoided open source Apache license libraries, to circumvent rigorous security restrictions that may be present in financial institutions

Tested and benchmarked a server solution to cater to 5000 simultaneous users. We built a messaging server for OTT mobile messaging a la Whatsapp. We built this on a combination of Dot-Net and SQL Server, Java, Hive, Jetty, Redis and RabbitMQ We simulated 5000 simultaneous…