It is no secret that migrating to Mule 4 from Mule 3 is a challenge. Mule 4 saw the biggest change in the Mule runtime since its inception. However, with this series of “Mule 4 migration made easy” blogs, I will attempt to soothe any pain you might feel while migrating and provide tips and tricks on how to make the best from Mule 4.
In my previous blog post, I discussed the basics of error handling with Mule 4, helped understand what a Mule error is, what the two major error handling scopes in Mule 4 are, as well as how they work. In this post, I will discuss how to take these basic concepts and build them up so that you can implement error handling strategies in your application (and not be completely lost when doing so).
Like many developers and architects who build APIs and integrations, I was on top of the world when I completed the training on Anypoint Platform Development fundamentals (Mule 4); I was now able to take an idea for an API and build, design, deploy, and implement my API in a matter of hours. I now held the shiny key to become a MuleSoft Certified Developer — I just had to pass the MuleSoft Certified Developer –
This is part four of my five-part series documenting high scalability in Mule 4. If you haven’t read part one, Scale your APIs with Mule 4, part two, Reactive programming in Mule 4, and part three, Thread management and auto-tuning in Mule 4, check them out! This post will cover streaming in Mule 4.
My first two posts in this Mule 4 blog series were on scaling your APIs and reactive programming in our newest version of Mule runtime engine. This blog dives into thread management and auto-tuning.
Mule 4 uses reactive programming to enhance scalability so our developers can deliver smooth experiences for their users.
Mule 4 addresses vertical scalability with a radically different design using reactive programming at its core.
One month into 2019 and we’ve already covered a wide range of content – from JSON logging in Mule 4 to work automation and API strategies. To provide you with the best posts to read if you’ve missed, here are the five most popular blog posts in January 2019.
This is a sequel to my previous blog post about JSON logging for Mule 3. In this blogpost, I’ll touch upon the re-architected version of the JSON logger for our awesome Mule 4 release while leveraging the (just as awesome) SDK!
We’re thrilled to announce the broad release of Mule 4 courses in our award-winning, in-demand, on-demand MuleSoft.U portfolio:
