In my last article, we saw how we can install Mule 4 on a Raspberry Pi. And while Mule 4 runs perfectly fine on the latest Raspberry Pi’s, you may find yourself in need of a more scalable solution than a bare-metal runtime installation. In this post, we will look at running Mule in a Docker container on Raspberry Pi.
We recently announced the GA release of Mule 4 and Studio 7, a major evolution of the core runtime behind Anypoint Platform. Over the past few months, we’ve discussed DataWeave, streaming, and building flows quickly and easily. Recently, we demoed these capabilities in the Mule 4 webinar, and we wanted to share this demo through this blog post!
What an amazing time it is! We recently announced a major milestone: the GA release of Mule 4!
The new release of Mule is all about ease of use and accelerating the speed of development. With up to 50% fewer steps and concepts to learn, Mule 4 jumpstarts integration projects with better access to data and a completely new reactive, non-blocking (and self-tuning) runtime engine!
An ObjectStore is a Mule component which allows for simple key-value storage. Although it can serve a wide variety of use cases, it’s mainly designed for:
If you are a Mule 3 user, then you’re already familiar with this concept. However, we feel that creating and defining these stores could be made much simpler.
A few days ago, we proudly announced the GA release of Mule 4 and Studio 7, a major evolution of the core runtime behind Anypoint Platform. Mule 4 enhances application development velocity with up to 50% fewer steps and concepts to learn, including a simplified language for connectivity, clear access to data, automatic tuning, and smoother upgrade processes.
We are very excited to announce the GA release of Mule 4 and Studio 7, a major evolution of the core runtime behind Anypoint Platform. Mule 4 enhances application development velocity with up to 50% fewer steps and concepts to learn, including: a simplified language for connectivity, clear access to data, automatic tuning, and smoother upgrade processes.
Today, we’re very excited to announce the Early Access (EA) version of Mule 4 and Studio 7. Mule 4 adds vastly more power, higher speeds, and greater simplicity into the famously small footprint of Mule – the industry’s leading all-purpose engine for building application networks. The Early Access release builds on the previous Mule 4 and Studio 7 releases, adding finalized APIs and DSL for early adopters and partners, Mule SDK availability,
The Mule 4 Release Candidate is here and, with it, the updated version of the batch module!
The batch module was first introduced in Mule 3.5 and it aims to simplify integration use cases where basic ETL functionality is needed. If you’re unfamiliar with it, I recommend you look at this post before continuing. If you are already old friends with batch, then keep reading for a breakdown of all the changes!
There’s a brand new Mule 4 Anypoint Connector for Database (DB) that you can use to connect to any relational Database engine. Unlike other connectors such as File or FTP, this connector has a pretty similar UX compared to the one in Mule 3.x, with some considerable improvements, including:
With the upcoming Mule 4 release, we’re working to deliver a simpler runtime, one that’s easier to use and run for all organizations. Today, we’re excited to announce the next step in that process: the Mule 4 Release Candidate! This release expands on the simplicity improvements in the Mule 4 Beta, adds new capabilities, and incorporates the great feedback from the beta.
