Things are shifting into high gear for the new year over at MuleSoft, and we’ve got two beta releases ready for everyone to kick the tires on: Mule 3.8 and Studio 6.0. The Mule 3.8 release is the first to bring together our Mule and API gateway runtimes in one single package. It also adds support in our high availability feature for multiple data centers with a new quorum feature. Studio features new API design round tripping with API Designer and DataWeave flat file support. And we’ve also greatly improved troubleshooting messages and the debugger.
Unified runtime for APIs and integration
When we first started our building our API solution, we created an extension of our core runtime specifically for API gateways. As time moved on, APIs became more and more central to everything we do, so in this release, we’ve unified the API Gateway extensions with the core Mule runtime, simplifying development and operations. Please see the migration guide for information on how to migrate.
API design collaboration across Studio & API Designer
Improved debugging and error messages
The Mule 3.8 runtime has improved error messages, which allow you to clearly see where the error is coming from, the payload at that point in time, the configuration for that element, and click to navigate to that point in the flow.
Mule HA Improvements
Mule HA includes a number of new improvements. First and foremost, it contains a new quorum feature, which allows you to specify the minimum number of Mule instances to function. This allows you to more effectively deal with network splits in a cloud environment, such as AWS and Azure. It also now includes a persistence option, which allows you to store data in the ObjectStore in a database. This improves resilience and allows you to create backups for recovery situations.
There are also many other enhancements in this release:
- DataWeave now supports flat files, allowing to parse files that have hierarchical structures in a text delimited or fixed length form.
- Users can now browse for WSDLs in the Anypoint Exchange and when configuring the WS Consumer.
- TLS improvements: TLS context can be shared in a domain, the cipher suite and protocol configuration is allowed per connector, TLS 1.0 is now disabled by default and there is a new “insecure” mode for local testing which doesn’t perform certificate validation.
- Support for nesting tests inside folders in MUnit and running multiple suites at a time.
Read the Documentation
- Read the release notes for Anypoint Studio and the 3.8.0 beta runtime.
- Read the documentation for the release
We look forward to your feedback in this post’s comments and in our forum. Happy connecting!