Anypoint Visualizer is a graphical visualization that provides a high-level view of your application network. It automatically organizes APIs, Mule applications, and third-party systems into a comprehensive view of how they are connected. The data displayed is dynamically updated based on real-time traffic and does not require any prior configuration.
As discussed in my previous blog post, the notion of the OODA loop is foundational for many of today’s common agile, LEAN and DevOps methods. But given we typically talk about it in a systems context, it’s important to examine the core motivations for enterprises becoming more responsive to changes in their environment.
In the 60 years since its foundation as a single gas station in Virginia, Pilot Flying J has grown to be the largest operator of travel centers in North America. With over 750 locations serving more than 1.6 million professional drivers and traveling motorists daily, Pilot Flying J provides its guests with overnight parking, showers, warm meals, Wi-Fi, and a vast array of merchandise.
After much hand wringing and collaborative sessions with teammates (most notably fellow Muleys Andrew Latham and Alison Jarris) and customers, a framework for how to think about agility has emerged that suggests a path about how to measure it (while not falling victim to Goodhart’s law).
Companies need to take the AI brain “out of the jar”; using application networks that enable AI to plug in and out of any data source or capability.
The fiscal year is ending and once again, your efforts to get modernization improvements funded haven’t planned out. You know that this lack of funding won’t stop any of your partners from decrying the competency or effort of IT.
The pace of change in customers’ expectations in an always-on, always-connected world has never been higher.
Developers play a crucial role in implementing an API-led approach for integration of applications, data, and devices to drive digital transformation. With the release of Mule 4, our goal is to empower you to cycle through projects with speed and velocity.
Many customers I meet are either evaluating or beginning their implementation of microservice architectures. Some of these customers are coming off big-bang projects that have failed to replace large legacy assets.
As an IT professional, have you ever been in a situation where you know something is broken, but you can’t manage to spot where it is coming from?
It is frustrating and quite time-consuming. You can try to use “divide and conquer” to determine the root cause. Step by step, you reduce the problem space until you isolate the origin of the issue. Yet, in most cases, you still don’t fully know what complex chain of events led to the pain.
