I am reminded of the classic Intel advert — our rock stars aren’t like your rock stars. The same can often be said for Integration; our solutions aren’t like your solutions.

The integration paradigm is just different. When implementing these solutions, we cannot approach them the same way as we would standard application development.

The way we think about integration solutions is different. The challenges are different. The errors are different and, by extension, so is the way we need to deal with runtime failures. Even the way we test integration solutions is different.

And therein lies the challenge! Many IT departments get tasked with delivering an integration solution. The problem looks more or less recognisable and so they assign the job to a team of competent and experienced developers. Usually, these developers have a solid background in Web Application, or Data-Driven Application, development.

With a competent skill-set and motivated team, they are up for the challenge and they quickly get to work — and equally quickly run into trouble. Within a few weeks or months, the team often realises that it has painted itself into a corner. A time comes when the solution starts to present with fundamental flaws that were not considered. These issues often look almost unsurmountable and impossible to unravel.

This is a pity as that pain can be so easily avoided. It is not that these developers are incompetent. All they lack is that crucial understanding of the integration paradigm and its specific idiosyncrasies. The right steer at the outset and a guiding hand from someone who understands the pitfalls inherent in the integration space, will save a world of pain.

If your company has recently acquired, or is considering, a MuleSoft licence — or if you are about to embark on a new integration project — it never hurts to bring in some outside expertise to consult or advise on the common pitfalls and challenges your team might encounter. In fact it might just make all the difference when it comes to the success of your project.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>