Coding Best Practices

Mulesoft Coding Best Practices

In this tutorial we have listed down some best practices that every mule developer should follow

• Avoid hardcoding values,hosts,urls and port number inside the mule code, try to use the properties files and refer the values from properties file inside mule code
• Avoid hardcoding the passwords in code, all the passwords should be encrypted use the secure property placeholder to manage the passwords
• Avoid logging the complete payload, it impacts the performance and security by logging the sensitive information
• User loggers with proper log level inside mule flows
• While logging the payload. Log only required information and mask the sensitive data
• Naming convention should be proper for system,process and experience API’s for mule projects and for flows and subflows, variables so that everyone can differentiate between all components
• Try to use common logging and error handling framework and use it across all mule application to maintain the consistency
• All possible runtime exception should handle correctly in mule code
• Response code should be mapped correctly as per HTTP standard
• MUnit should be written for all the mule flows and test coverage should be greater than 80 %
• Try to do the validation on fields in well advance at the starting of the mule flows
• It is recommended to use the latest mulesoft connector version in pom.xml
• Avoid duplicacy inside mule code, try to wrap the reusable code in subflow/flow and use across mule application
• There should not be any unused variable/code inside mule project
• All the dependent 3^rd party library should be added as dependency under pom.xml
• Should not load large file or payload in to memory
• Avoid creating copy of the payload and store in variable
• Reprocessing connection strategy should be implemented in case of technical fault