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.
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.
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?”
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
Today, we released Mule 4 beta, which 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. I couldn’t be more excited. With Mule 4, we’ve delivered a simplified language for connectivity, transparent data access and streaming, automatic performance tuning and smoother upgrades. It’s a major evolution of the core runtime of Anypoint Platform.
This week, we sat down with Andrés Curcio, a Software Developer in Test on our Core Services Testing team in our Buenos Aires, Argentina office. Our Engineering teams are small and cross-functional, so testers have the opportunity to lead both team-related and product-specific responsibilities. They partner and collaborate with front- and back-end engineers across teams in order to improve our testing processes.
A recent report by Rightscale, which surveyed 1,002 technical professionals, revealed that respondents run 41% of their workload in public clouds. A number of market research firms estimate that the public cloud market value will reach between $195B and $236B by 2020. Within this public market, Amazon continues to maintain its leadership position.
To serve our customers needs, we have introduced a number of Amazon connectors in the past – including S3, SNS, and SQS – in order to enable our customers to easily connect to Amazon Web Services.
Neo4J is a leading, open source graph database designed to leverage data relationships as first-class entities. It was initially developed in 2000, and became an open source project in 2007. Since then, it has been adopted by over thousands of organizations including Walmart, Marriott, UBS, Cisco, HP, and eBay.
I am excited to announce a new version of our open source API console. The 4.0 release comes with a completely new and responsive UI, improved capabilities for trying out your API, and additional tools to integrate automated builds into your CI/CD pipeline.
The API console can be run as a standalone web application or easily integrated into your own website, making it easy to incorporate into an existing developer portal with a fully branded layout. We are also looking forward to the new API console becoming fully integrated into Anypoint Platform with upcoming releases.
I work as a Product Manager for the Platform Core Services team at MuleSoft. My team works primarily on Identity and Access Management services, platform sign ups and logins, audit logging, and entitlement services. My team is unique in that the consumers of our services vary from external customers to internal teams such as Support, Sales Ops, Finance, and Product teams. We are like the glue that holds the different components of Anypoint Platform together.