GraphQL offers a new style of API design intended to provide API consumers with unified access to back-end data and services. In spite of this seemingly universal aim, GraphQL has created a schism in the API community between those who believe it is superior to state of the industry RESTful API design and those who believe it is naively re-introducing solved API design problems. This blog examines GraphQL, the API community’s dichotomous emotional responses,
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.
Asynchronous messaging enables applications to decouple from one another to improve performance, scalability, and reliability. This post will review the most common messaging patterns, along with why and when to use them.
Many modern applications are built using microservices. The reasons are well documented: microservices are smaller, targeted applications that foster agility and are much easier to manage. However, as more microservices are built, often with different languages and deployment models, organizations end up with complex environments that can be costly and difficult to operate. This complexity can stifle innovation, negating the promise of microservices.
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.
In 2018, there were 6,500 data breaches reported, exposing billions of records for potential misuse. In today’s digitally connected world, security is almost always top-of-mind for businesses to keep their records are safe and secure. It’s critical for organizations to implement API security best practices to keep their integrations and the data that travels between systems under tight lock and key.
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.
The Developer Relations team has been listening to your feedback which was many requests for more introductory educational content. As a result of your comments, we launched a single catalog featuring self-paced, step-by-step developer educational tutorials to learn how to build your first API or integration with MuleSoft’s Anypoint Platform.
Univar Solutions is a leading global distributor of specialty and basic chemicals. With 800 distribution facilities and a network of 8,000 producers worldwide, we rely on our operational excellence to provide customers with reliable deliveries, while offering cost competitive products. We operate in a heavily-regulated environment, sell entirely B2B, and have grown heavily through acquisition.
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.