We often expose the proxy APIs that connect applications to their backend APIs. With a proxy API, the application continues to run without issue and continue to call and connect to the backend API while a developer is editing it. Exposing a proxy API also protects the backend API from the world, shielding the real IP address.
The advantage of using a proxy is having a layer of separation to ensure that any attacks against our API are stopped well before anyone interacts with our main servers.
As part of our upcoming Anypoint Platform June 2016 announcement, we are excited to release Mule 3.8. This release extends the flexibility of Mule, the runtime engine of Anypoint Platform, by unifying integration and API management capabilities into one lightweight distribution. It also significantly enhances core Mule functionality including DNS round robin load balancing, DataWeave Flat File, Fixed Width and COBOL Copybook support,
When deployed as an API Gateway and managed with API Manager, the highly performant Anypoint Platform enables you to control which traffic is authorized to pass through your APIs to various backend services, meter the traffic flowing through your API, log transactions, and apply runtime policies.
A policy is a mechanism the gateway uses to enforce filters on traffic as it flows through the gateway.
I’m pleased to announce the availability of our Anypoint Studio 5.3 release with the brand new Mule 3.7.2 release. This release features a new validations module, which allows you to easily validate Mule messages using a variety of built in validators. It also features many improvements such as improved ability to attach sources to runtimes and improvements to the API gateway runtime experience in Anypoint Studio.
The latest release of Anypoint Platform includes major upgrades to our logging service for applications running on CloudHub (now a Platform service). With this release, users will be able to retain more log information per application, using a globally distributed infrastructure, and access the logs via an updated UI. Additionally, users who do hybrid management of on-premises servers and applications will now be able to set up High Availability (HA) for their on-prem servers using the new clustering feature.
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,
I am extremely happy to announce a significant set of updates to Anypoint Platform for APIs that were introduced this month. These updates will make it easier for API owners and administrators to publish their APIs in a way that is sure to further their successful adoption. The sections below describe the core new capabilities introduced in this release.
The general guiding principles of the Zen philosophy can actually be quite helpful in designing the Anypoint Platform for APIs‘ deployment architecture. The emphasis on having a holistic approach, while striving for simplicity, symmetry, and minimalism, works as well for meditation as for coming up with a stable, robust and secure architecture. Here, we will outline the four most common models in use today that dovetail with the teachings of the Zen philosophy.
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.