If you ever used Mule 3, then there are probably two things about error handling you already know:
- It’s really Java exception handling
- It’s a “trial and error” experience
In this post, I’ll explain the major changes introduced in Mule 4 around error handling, including easier routing and the introduction of our new try scope.
In my role at MuleSoft, I advise federal agencies and commercial businesses in connecting their applications, data, and devices. Those conversations center around building modern Application Programming Interfaces (APIs) to create new capabilities. A modern API is one that enables systems to exchange information securely using broadly adopted standards like REST and JSON.
Over the past few months, I have been working with our Product and Engineering team on Crowd, the latest release of Anypoint Platform. The Crowd release consists of updates to Anypoint Exchange as well as the new Anypoint Designer Center in Anypoint Platform.
This release will further drive business agility by streamlining the consumption of assets from Anypoint Exchange, allowing teams to build integration projects and design API specifications much faster than ever before. I am sure you are thinking: “But, how?”
Streaming in Mule 4 is now as easy as drinking beer!
There are incredible improvements in the way that Mule 4 enables you to process, access, transform, and stream data. For streaming specifically, Mule 4 enables multiple parallel data reads without side effects and without the user caching that data in memory first.
A lot of people are not familiar with the concept of streaming. So before we get into the specifics of streaming with Mule 4; let’s first go through a couple of use cases that highlight its value.
In the month since our launch, the community has responded enthusiastically to the launch of our new MuleSoft Meetup program. These Meetups are community-led events, bringing people together to explore, teach, and learn about API-led connectivity by sharing use cases and doing hands-on exercises. You don’t necessarily have to be a MuleSoft user to join: all API enthusiasts are welcome!
Today you’ll meet the newest member of our Training Talks series, Mark Nguyen. Mark joined the training team in November of 2016 as a Curriculum Developer, and will be a familiar face from now on! And yes, we have Mark’s fun fact too…are you ready?
Mark was part of the original team that launched Taco Bell’s Doritos Locos Tacos and, from what I heard, if you mention his name when ordering one, you’ll get an extra taco for free. (Just kidding, I tried it though!).
An API fragment is a portion of an API specification, which is why understanding it starts at the API specification level. An API spec consists of a plan of how your API should look structurally – like a blueprint of a house.
The API spec documents what an API does and the expected call and response you can expect from it. It’s a key part of API development because it can help you isolate design flaws or problems before you write a line of code. A way to create APIs more efficiently is to get reuse by reusing portions or fragments of APIs into specs.
All hail DataWeave!
One of the major changes in Mule 4 is the introduction of DataWeave as our primary expression language. Although this may seem like a radical change, I’ll explain some of the reasons behind our decision, and why this represents a major leap forward. I’ll also share some examples and answer a question that is likely on many readers’ minds: “what about MEL?”
Our favorite drummer/instructor is back with a new edition of Training Talks! In this demo, Ethan will show you how to copy over global configuration elements from a Mule application into a Mule domain project, including copying over the namespace and the schema location definitions for those global configuration elements, including the HTTP and VM queue connector.
Follow Ethan’s demo by watching the video above and reading the instructions below:
I’m very happy to announce the beta version of Studio 7, which not only offers support for the Mule 4 Beta runtime, but also improves the overall user experience for Studio users.
In this blog post, I will walk you through some of the biggest UX improvements and architectural changes that will transform your user experience:
As a quick summary, Studio 7 will offer:
- Transparent and easy Maven integration