AVIO Consulting

Bootcamp Increases Mulesoft Adoption and Efficiency

Jan 1, 1970 | Case Studies

The client is a National Retail & Entertainment company working on the MuleSoft platform for almost a year and has written multiple APIs.

The Challenge

The client’s team wasn’t really making the most of the platform’s value. This was primarily because they lacked practice. The team was keen on adopting it and wanted to do things in the right way. However, they did not know how. This came as a big challenge to them.

To mitigate the challenge, AVIO came up with a two-step solution.

The Solution

The Senior Developer of AVIO opened up different projects and checked their architecture. This gave him an idea about a few things: 

  • The support technologies they are using like CI/CD tools and Jenkins
  • The testing suites that they are using and how well
  • Cloudhub environment and architecture
  • Logging framework
  • Development methods 
  • The process to connect to the on-prem systems from the cloud
  • The good and the bad practices

After this, the company came up with activities like: 

  • Opening projects and reviewing them one by one
  • Group discussion and interviews
  • Roadmap review

AVIO decided to implement a mini Bootcamp to train the client’s team. Other goals included sharing knowledge regarding best practices and offering examples of documentation. 

Our logging framework was highlighted with the MuleSoft environment adoption. We decided to refactor the underperforming code to ensure it performs better. 

The Bootcamp

For the training materials and agenda, we created a client space inside the Atlassian account. This space was for the team, as well as their client. It contained the pre-requisites, topics, and exercises. 

Additionally, we introduced a few programming exercises for refactoring code, to reinforce adhesion to the best practices taught during the Bootcamp. 


For reinforcing the practices that were learned at the Bootcamp, the AVIO developers and the client developers had been paired together for refactoring the existing process using a 3-step procedure. 

Prior to the coding exercise, AVIO developers analyzed the code and singled out the areas that need refactoring. 

  • In the first phase, AVIO led the development work, and the client’s team served as the audience.
  • In the second phase, the client’s team was the one to lead the exercise. 
  • Ultimately, in the final phase, the client developers made the required change and initiated the Pull Request to the developers of AVIO to review before they merged the changes with the main code.