If you have read the Mule ESB 3.7 release notes then you already know what I’m about to say, but just to recap, here we go…
A lot of effort was put in 3.7 to upgrade our libraries stack. That effort actually began in 3.6, and although the list of upgraded libraries is not so big as it was on that release, it’s somehow more significant given that we upgraded some dependencies that we held very close to our hearts and core.
The idea of this post is to clarify some concepts around metadata, what is it, where is stored, how to use it and how it help us to develop our applications.
So, what is it? Metadata is a term used in many places in the Software industry and its meaning may vary depending on what it’s used for. In the context of Anypoint Studio we are always talking about types and types related information.
A high-reliability application (one that has zero tolerance for message loss) not only requires the underlying ESB to be reliable, but that reliability needs to extend to individual connections. If your application uses a transactional transport such as JMS, VM, or DB, reliable messaging is ensured by the built-in support for transactions in the transport. This means, for example, that you can configure a transaction on a JMS inbound endpoint that makes sure messages are only removed from the JMS server when the transaction is committed.
Testing is essential to all code, it’s a warranty on the expected behavior and a measure of quality. Having a large and thorough test suite increases the confidence we have on a system. That’s why Mule offers a number of options for testing, like our Functional Test Framework or MUnit, a good example of the former being FunctionalTestCase. By extending from this class we can create our own tests around a Mule configuration XML file (or many) that will be run as an app in a Mule server.
Did you know Healthcare and Life Sciences organizations are leveraging MuleSoft to radically transform healthcare? Providers are extending the point of care beyond the four walls of the hospital ward, and health insurance companies are moving from passive payers of claims to active managers of their policyholders’ lifestyle.
MuleSoft’s Anypoint Platform enables these transformations by providing a new level of connectivity. To thrive in this new era,
We’re happy to announce the 1.0 release candidate of MUnit – the unit and functional test framework for Mule. This is our first official release of MUnit and incorporates major usability improvements, broader support for Mule components and many bug fixes.
Today, the Mule 3.7 runtime and Anypoint Studio June 2015 are now GA. This release brings to a close over two months of product announcements impacting nearly every aspect of Anypoint Platform. It also marks the beginning of a new way for our user community to experience our products — less as a collection of rich independent capabilities and more a unified platform with unified tooling and unified management to help users deliver value with speed,
A few years ago, a MuleSoft engineer had a vision. That vision: automated testing for Mule applications in Anypoint Studio. As this developer’s focus was building Mule applications to connect SaaS apps, a validation framework would significantly reduce development time and increase productivity across teams. More specifically, unit tests would allow this developer to mock dependencies, uncover problems early, refactor applications quickly, and provide agile documentation for other Muleys.
In a previous blog, we talked through how you might design a solution to deliver a Command Query Responsibility Segregation (CQRS) pattern with Anypoint Platform. In this blog, we’ll discuss how an API-led connectivity approach can help you deliver this pattern (and the mobile application your business is demanding) with speed and scale while maintaining control over your critical data assets.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.