Deployment options of Anypoint Platform

This blog describes Mule and Anypoint Platform deployment options and maps them to the most common use cases and customer needs. 

Before diving into existing capabilities and the most common use cases, let me start by sharing how MuleSoft products have evolved over time. 

Digital transformation (DX) engine scenario

In my first blog, I explained what digital transformation is, why connectivity and integration is vital for a successful digital transformation, and how MuleSoft’s Anypoint Platform is an engine to power that digital transformation.

In this blog post, I’ll be using a common digital transformation initiative in the domain of digital customer experience (DCX) as an example: “Enhanced customer sales experience.”

The perfect service-abstraction and composition solution: MuleSoft Anypoint Platform

This blog post is based on the internal work of Thomas Baumgart, former MuleSoft Client Architect, and is now being published by MuleSoft.  

This is the third blog in a series explaining how MuleSoft’s Anypoint Platform can provide agile connectivity across monolith, SOA, and microservices architectures.

Anypoint Platform quarterly FAQ: Q3 2019

As the old saying goes, “If you have a question, it’s likely many other people are wondering the same thing.” That’s why we are introducing the first installment of our Anypoint Quarterly FAQ where we answer our customers’ most frequently asked questions. 

This quarter, we will be focusing on questions surrounding the Anypoint Platform October release. If you haven’t caught up with our most recent release, download this two page executive executive summary which highlights all new and updated components of our platform.

Error Handling with Anypoint MQ

error-handling

In a modern cloud architecture, one of the common patterns that is observed is the use of message queues to: 

  • Decouple applications
  • Improve performance
  • Increase reliability
  • Implement granular scalability

Introducing Connected Apps in Anypoint Platform

This blog post describes newly released capabilities within access management and maps them to most common use cases for Anypoint Platform.

MuleSoft’s APIs allow developers to extend Anypoint Platform capabilities, adding flexibility and reducing friction in day-to-day workflows. With its latest release of Connected Apps, developers can use standard OAuth 2.0 and OpenID Connect protocols to authenticate users, provide Single Sign-On, and issue tokens to use with Anypoint Platform APIs.

Mule 4 migration made easy: migrating the Choice router

October 11 2019

0 comments

Routers in Mule implement the Message Router pattern described in the seminal work on integration patterns: Enterprise Integration Patterns, Gregor Hohpe and Bobby Woolf. Addison-Wesley Professional; October 20, 2003. They allow you to route a Mule event from one Event Processor to one or many Event Processors.

Beyond MuleSoft Development Fundamentals: Mule 4 Logging

Logging is useful for monitoring and troubleshooting your Mule applications and the Mule server — whether that’s recording errors raised by the application or specific details, such as status notifications, custom metadata, and payloads.

Mule 4 migration made easy: migrating the Enricher

The Content Enricher is a useful content transformation pattern that elaborates a basic message with information from another system. A typical use case is described in the seminal work on integration patterns: Enterprise Integration Patterns, Gregor Hohpe and Bobby Woolf. Addison-Wesley Professional; October 20, 2003. It describes a scenario where one system may provide a customer ID, but the target system requires the customer name and address. This additional information must be retrieved from another system and combined with the customer ID to form the information required by the target system.

Intro to API Community Manager

API Community Manager

Because APIs make digital assets easy to reuse and deliver, APIs power virtually every digital experience. Even more important are the developers who create, connect, and translate APIs into digital experiences. Yet the experience provided to these developers is often just a static website with technical documentation about your APIs