Mule flows - Naming conventions

Question

As with any programming language, what are the standard naming conventions to be followed while writing Mule flows? I found camel-case convention has been followed in Mule in Action book.What is the standard format for Mule naming convention.

Can any suggest the standard option?

Answer 1

There is no such thing as a naming convention for Mule. You could try to apply the same rules Mule community developers follow, but those are not strictly for Mule Applications.

At the same time it does make sense to follow the same naming conventions than the IoC container of Spring given that Mule is a sort of specialization of it.

Answer 2

I've made a training on MuleSoft "MuleSoft.U Developer Essentials" and all the flows they named was like that: nameOfTheFlow. So the first character was always at lower case and the name always ended with "Flow". Also, the first word was always what the flow was doing, for example: "getPermissionsFlow" or "postUserFlow". So, based on my experience, that was the convention the course brought to me.

Answer 3

There is no specific naming convention thumb rules. Java naming style would be good. Most of the case the enterprise for whom your are developing the application will hold their own naming convention standard.

Based on my experience naming conventions with a defnite symantics eg MF_Employee_RegService were MF is mule flow , Employee department , Registration service

camel-case is also a good option.

Answer 4

You can define your own There is no compulsion. For better maintainability and readability you can prefix targetSystemName for the flows which Hits the endpoint fallowed by the activityName that the flow accomplishes example:crm_fetchCustomerDetails, you can prefix common or util fro the flows which are common across your project.