Hi folks, in this fourth post of the new Mule Agent blog post series I will introduce the Mule Agent architecture and the main advantages it provides.If you missed the previous posts in this series, check them out below:
During its development,
This blog post is the third in the new Mule agent blog post series.
You can access the first two blogs here:
- Introducing the new Mule agent
- Mule Enterprise Management and the new Mule agent
In this post, I’m going to talk about some of the common use cases we envisioned for the agent as we were developing it.
The vision we had when building the agent was that it would be the primary interface to access the Mule runtime.
This is the second of a series of blog posts around the new Mule agent. For an overview of the new Mule agent, be sure to read Introducing the new Mule agent. In this post, I’ll talk about the new agent in relation to the Mule Enterprise Management Console (also known as MMC).
Readers of this post are probably familiar with MMC,
Together with the release of Mule 3.6, we’ve also shipped a new Mule agent that exposes new APIs to manage and monitor running Mule, enhancing the experience of creating API-led connectivity in a big way.
The new Mule agent exposes APIs that allow enterprises to tie easily into their existing SDLC processes and applications. The agent also has a flexible framework that’s quickly customizable to meet new operational governance requirements around Mule.