The biggest priority for our tooling continues to be ensuring developer productivity with Mule 4 and Anypoint Studio. However, developer productivity doesn’t apply to just the individual developer, it also applies to teams of developers. With our recent releases, our focus has been to bridge the critical gaps faced by development teams. Today, we are excited to share the new features that come with Studio 7.5 and 7.6, including the ability to collaborate on API specifications with your teammates.
This is the second in a series about JSON logging. If you want to customize the output data structure you can check part 1 of the blog post. In this post, we are going to explore the new capabilities added in version 2 that were implemented based mostly on user feedback.
In May 2020, we announced the general availability of Mule 4.3, Studio 7.5, and MUnit 2.5. This release concluded a long internal journey with several objectives: hardening and stability, performance parity between Mule 3 and Mule 4, and closing developer productivity gaps (API specification lifecycle in Studio) in Studio 7. As we made this release public, we achieved an important milestone in Mule 4’s evolution. Mule 4.3 is now better-equipped than ever before to welcome Mule 3 applications into Mule 4.
Picture this: you’re buying a new car. Should you upgrade your vehicle to get better features? Usually, you’re buying a vehicle to drive it — but, thanks to technology, there are dozens of other reasons to upgrade. Your current ride probably doesn’t have the latest safety and convenience features, and your warranty has likely expired. So, should you hang on to your old wheels? Think about cost, safety, and connectivity. If your mechanic is spending more time with your car than you do,
Alexandra Martinez is a member of our Developer Community and has been leading our Meetup Group in Toronto for a few years now. She brings her local community together on a regular cadence, each time with more and more attendees. For more information on how to join the MuleSoft Community, visit our Community page.
Before this app, our HR department at Bits In Glass (BIG) was manually posting messages to different Slack channels in our workspace.
It’s important to monitor your service and check if it is available and/or is performing as expected. To do this, we need to understand what service health means. In this article, I will present two different definitions. However, keep in mind that your project can have its own specific definition as well.
All examples are prepared in Mule runtime 4.2. If you are familiar with Spring Boot Actuator you should see some interface similarities.
At some point, you may have a service that returns a lot of fields and related objects. What if the service consumer doesn’t want all the fields all the time? In other words, they would like to have the response filtered. This is where the Content Filter comes to the rescue. After you read this article, you will learn how to use it in your own scenarios. So let’s roll!
Ensuring developer productivity with Mule 4 and Anypoint Studio has been a core priority for MuleSoft this year. We’re excited to announce the GA of Anypoint Studio 7.4, which comes with Mule 4.2.2 and introduces native OAS support, dependency management, and API search capabilities to accelerate API development.
Routers in Mule implement the Message Router pattern described in the seminal work on integration patterns: Enterprise Integration Patterns, Gregor Hohpe and Bobby Woolf. Addison-Wesley Professional; October 20, 2003. They allow you to route a Mule event from one Event Processor to one or many Event Processors.
The Content Enricher is a useful content transformation pattern that elaborates a basic message with information from another system. A typical use case is described in the seminal work on integration patterns: Enterprise Integration Patterns, Gregor Hohpe and Bobby Woolf. Addison-Wesley Professional; October 20, 2003. It describes a scenario where one system may provide a customer ID, but the target system requires the customer name and address. This additional information must be retrieved from another system and combined with the customer ID to form the information required by the target system.
