I'd recommend to invest in staff training upfront and carefully understand the licensing model and your data usage. I would suggest understanding how the licensing model works and how your data flows. This will give you a clearer notion of how much you are going to pay (potential cots). We invested a lot of time figuring out the implications of CPU usage, message rates, memory usage, as well as our data's origin and destination. This allows us to understand the true financial impact of MuleSoft Composer. Without this understanding, you might face unexpected costs. Overall, I would rate the solution nine out of ten.
