Guide to API synchronization with Studio 7.6

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. 

Everything you need to know about observability in Anypoint Platform

Observability is a comprehensive set of capabilities around logging, analytics, monitoring, troubleshooting, and measurement of a system. Here the term system is broadly used to indicate platform, runtimes, and applications. Observability plays a consequential role in providing the real-time pulse of a system. Lacking observability in a system would be similar to flying an aircraft without a fuel indicator.

Setting up Anypoint VPN with Google Cloud Platform

There are a variety of ways to establish connectivity between Anypoint CloudHub workers and systems deployed on backend customer-hosted or vendor-managed data-centers. One of the ways is through Anypoint VPN which provides a secure tunnel between cloudhub workers and  a data-center. In order to setup the VPN tunnel or extend the CloudHub network with corporate network, we need to setup Anypoint VPC. Anypoint VPC provides an isolated network segment to host CloudHub workers. 

Drive API adoption with OAS 3 in Anypoint Platform

As organizations expand access to their services by productizing APIs and exposing them through developer portals, developers are looking for easy ways to understand and consume these APIs. API description formats like the RESTful API Modeling Language (RAML) and the OpenAPI Specification (OAS) provide a way for users to understand and interact with these services without needing to understand the underlying implementation logic.

Mule 4 migration made easy with Mule Migration Assistant

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.

A deep-dive into sizing your Runtime Fabric cluster

Runtime Fabric has consolidated as the most flexible deployment option for the Mule runtimes. Anypoint Runtime Fabric can be installed in your on-premises data center or cloud-hosted environment (Azure, AWS). This type of deployment is similar to that of CloudHub in that it offers high availability and has zero-downtime for data centers.

What to expect when you’re expecting: application network edition

I joined the MuleSoft Customer Success (CS) team in mid-2019 which was the beginning of a new adventure for me in many ways. I was out of my comfort zone — both in terms of my new role and the technology platform. Throughout my career as an integration consultant, I focused on how to get the data from source to target using drag-and-drop desktop tools. It did not take me long to realize that, at MuleSoft,

MUnit testing made easy: Introducing the test recorder

Testing is an essential part of the software development process used to ensure code quality, but the reality is that it can be a daunting and arduous task — especially in larger applications. This can make it difficult for some users to know where to begin when they’re ready to test their Mule applications in MUnit.

Improved threading model in Mule 4.3

When first released, Mule 4 introduced a brand new reactive execution engine and threading models. Benefits include high scalability, back pressure capabilities, and auto-tuning.

As part of Mule 4.3, we reiterated on these and made further improvements. More specifically, the three thread pools were combined into a single thread pool. Before jumping into the details, let’s quickly summarize how the threading models were set up prior to this release.

API governance: Asset approval process

In our previous blog, we covered the overview of governance posture for organizations. In this blog, we will take a deep dive into identifying the family of assets in the API ecosystem and their approval process. The aspects covered in this blog are highlighted in orange in the image below. As with any initiative an approval process spreads across different pillars and stages of the governance process as shown in the following matrix.