Similar to the Salesforce World Tour, MuleSoft CONNECT is MuleSoft’s conference series bringing people together around integrations. It’s a great place to learn about how to design, build, and manage integrations and APIs to meet IT and business goals. With this in mind, we sent two of our team, Nkosi Ncube and Salesforce MVP Mike Gill to the London edition. Here’s Nkosi’s takeaways from his time at the event:

Mike and I had an interesting two days representing Cloud Galacticos at MuleSoft CONNECT 2019 London. We were there to find out more about MuleSoft and the concept of API led connectivity to see where it could be of use to our growing list of clients. The workshops were fun and interactive, and the examples, case studies and keynotes were really interesting: “Innovate or die” will soon be replaced by “Connect or die”.

The conference was an insightful introduction into the MuleSoft concept of API led connectivity – integration through reusable APIs, which play specific roles. Lack of connectivity can be damaging to businesses that don’t open up to other organisations or partners, stopping synergies and business partnerships that can be formed through flexible but secure API connectivity.

What MuleSoft offers to the integration space is a way to get rid of the tangled web of connectivity which can slow down change in some organisations, particularly those with legacy systems. Historically, integrations require a lot of development time and cost, and prone to failure. Over time the connections become a tangled web of point to point connections that are difficult to manage and maintain, especially as more integrations get added on.

API led connectivity involves three layers of APIs; Systems, Process and Experience Systems as illustrated below.
MuleSoft Layers

If one of our clients at Cloud Galacticos is developing a mobile app, the developers would just concentrate on just developing the mobile app not the APIs because they have access to reusable assets from the System and Process API (for connection to Salesforce or other legacy systems), hence development time considerably is reduced money is saved in the process. Therefore API led Development reduces IT projects failure. These small reusable APIs are sometimes called microservices and are something our team have been talking about for a while – you can see our COO Paul Battisson speaking at Dreamforce here and here.

All in all, Mike and I had an insightful couple of days in London. We’ve learned a lot, and look forward to putting our newly acquired knowledge to good use! If you would like to talk to us about how you could use an API-led approach to enhance your organisation, or are just looking for some Salesforce help in general, please reach out using the form below.