My experience with MuleSoft Integration in Polarising’s team.

mulesoft image featured

Six months have passed since I joined Polarising. Time flies when we are excited getting to know a new company, new people, and new ways of working.

But for me it has also been an exciting time to learn and challenge myself, especially because I started to develop my knowledge in MuleSoft Integration, an innovative technology based in one platform for APIs.

Polarising is strategically investing to become experts in MuleSoft. This partnership will contribute to our Integration portfolio, offering clients the expertise in a technology that is leading the easy and platform-free APIs application delivery.

Knowledge shared within the best team.

As part of the MuleSoft team within the Integration area, our first mission was to set up a good library for internal knowledge sharing. We gathered all sorts of materials from our trainings, like tutorials, tips, and other interesting articles that we come across from MuleSoft’s sales and development areas.

This gave us the opportunity to write some of our own technical content:

  • An insight into all MuleSoft levels of certifications (MCD, MCIA, MCPA) and the right path to complete each one, as well as the definition of a study plan to achieve them.
  • Compiling relevant content from MuleSoft Meetups across the world; it’s usually at these events that good practices and technical knowledge is shared, opening the discussion to new insights.
  • The preparation of a blog article about a particular proof of concept that we have made titled “Mulesoft with Log4j or JSON Logger, published at Polarising’s technical blog.
  • Elaboration of internal technical tutorials, for example, on how to create a common library for general use in MuleSoft applications.
  • Tutorials about other technologies that have connectivity with MuleSoft, like Logstash – Read JMS Message from ApacheMQ, Filebeat – Read ApacheMQ Server Logs.
Image: MuleSoft Anypoint view.

We already knew that the MuleSoft community was large and diverse because they promote several theoretical and practical events. But entering their world gave us broader teachings that will be useful to us in order to continue to improve our knowledge.

My team and I are very committed to continue learning, so we have also participated in some events. One of them was MuleSoft PKO 2022 a partner focused event that approached all Mulesoft’s ecosystem, starting by their strategy and product vision, and partner program innovations and training offers.

First steps to a successful business Acceleration / Integration.

I started by taking the MuleSoft Certified Developer certification a couple of months ago, and recently the MuleSoft Certified Integration Architect. I believe that investing in certifications is important to understand MuleSoft’s content and to reduce the risk of development errors.

Image: MuleSoft Certification badges.

I have also joined other courses more related to the business, as learning an accelerator (adapted code) so that it can set an example (template) for data maintenance between Salesforce Health Cloud / Cerner, according to the MuleSoft practices.

As a result, I got my “Accelerator for Healthcare Champion” badge. This badge doesn’t represent only a level of certification, but also the know-how to use this template for the associated use case. It also allows us to analyse the code logic that exists in these templates and adopt it to other use cases.

Image: MuleSoft Accelerator for Healthcare Champion course completed.

The first challenge.

Image: Framework.

The first field presentation we made was a POC to expose a client’s case-study. It consisted in developing three APIs within a system with the following requirements:

  • Expose two store-procedures from a MySQL database.
  • Expose a public service WSDL.
  • Include error-handling in common library for all API’s, encryption of parameterizations and use HTTPS (with security certificate).
  • Application security layer (API Discovery, Client ID Enforcement and use of other policies).
  • Use of Domain-Project.
  • Deployment in CloudHub and in a Hybrid On-Premise system.
  • Creation of a framework for Log analysis and interpretation (use of ApacheMQ and ElasticSearch Stack).
  • Finally, the inclusion of CI & CD through BitBucket, Artifactory and Jenkins.

Image: Monitoring applications in MuleSoft.

We are very excited to begin this journey with MuleSoft. And I am positive that Polarising’s team will respond to our clients’ needs of integration with robust solutions that allow a seamless integration with new and legacy systems, leveraging re-usage across platforms.

Nelson Luz
Senior Integration Engineer at Polarising

To know more about Polarising’s integration services, visit our website.

Author profile

Software Engineer