Mule … ▪ Instead we did a qualitative and quantitative comparison of major open source ESB products using different criteria: ▪ Primary: professional maintenance, commercial support with SLAs, licensing, performance, operations by IT department possible ▪ Secondary: documentation, code quality, activity and size of community, Spring support, sync and async communication, supported standards, app server integration, development tools ▪ Mule quickly emerged as the favored ESB product, followed by Fuse ESB and WSO2 ▪ Static analysis of the Mule sources (Sonar, Structure101) showed acceptable quality ▪ Modularization and project structure looks well- thought-out and enables light-weight deployment ▪ Good code quality, in spite of found violations and partially low documentation ▪ T est coverage is reasonably high to ensure correct function in case of changes How and why we selected Mule Based on the proposed architecture scenarios we could identifythe requirements on the ESB product RAMYA