The reality of supporting production event-driven architecture at any reasonable scale is that it can be challenging, especially when dealing with bad events and unhappy paths, both of which affect business operations and the customer experience. Architects and developers often focus on delivering the minimum viable product (MVP) to show business value early and validate the approach taken. While focusing on the MVP can be valuable in establishing IT agility — the requirements are targeted at normal operation,
Veera Gopalakrishnan, a System Integration Engineer, and Swarnim Ranjitkar, a Sr. Software Engineer, at University of California, San Francisco (UCSF) both have more than five years of MuleSoft experience. Veera presented a UCSF and MuleSoft use case during our Developer Meetup at MuleSoft CONNECT Digital Americas. Here, Veera and Swarnim provide an in-depth explanation of how UCSF uses dynamic DataWeave scripts and the Salesforce platform for secure access to Electronic Health Record (EHR) data through APIs.
A number of the materials (posts, tutorials, etc.) available out there present an approach to integration between MuleSoft and Salesforce on the basis that MuleSoft is always proactively responsible for starting communication, injecting or pulling CRM data based on a schedule or otherwise.
This post aims to present a different approach to integration between these two platforms, where MuleSoft works in a more reactive way, triggered by notifications (events) sent by Salesforce representing new or modified data,
Our Meetup groups have scheduled another packed month of virtual events! Throughout July, you’ll have the opportunity to join local virtual Meetups from anywhere in the world, and both our Online Groups in English and Spanish will also be holding global virtual events. MuleSoft Meetups provide great opportunities to learn from MuleSoft experts, meet our Community leaders, and share your own expertise in trivia games. Use #MuleSoftMeetups on social media to let us know which events you join.
As organizations expand access to their services by productizing APIs and exposing them through developer portals, developers are looking for easy ways to understand and consume these APIs. API description formats like the RESTful API Modeling Language (RAML) and the OpenAPI Specification (OAS) provide a way for users to understand and interact with these services without needing to understand the underlying implementation logic.
Our MuleSoft CONNECT Digital events offered a multitude of opportunities for developers from around the world. Developers could attend developer-focused breakout sessions, join a Meetup group, and earn MuleCoins for MuleSoft swag. If you attended one of these events, thank you! It was a pleasure virtually meeting everyone. For those who missed our events, check out our recap and Developer Meetup recordings below!
In May 2020, we announced the general availability of Mule 4.3, Studio 7.5, and MUnit 2.5. This release concluded a long internal journey with several objectives: hardening and stability, performance parity between Mule 3 and Mule 4, and closing developer productivity gaps (API specification lifecycle in Studio) in Studio 7. As we made this release public, we achieved an important milestone in Mule 4’s evolution. Mule 4.3 is now better-equipped than ever before to welcome Mule 3 applications into Mule 4.
Welcome to Mule Invaders, the video game inspired by the classic retro shooters Galaga and Space Invaders. In Mule Invaders, help Max the Mule destroy waves of enemies by spawning powerups using APIs. To protect Max on his journey to integrate the universe, create APIs in Anypoint Platform, deploy your application on CloudHub, then make HTTP requests to your APIs to spawn powerups while playing the game in realtime. When you use a REST client to send a POST request to your API,
Runtime Fabric has consolidated as the most flexible deployment option for the Mule runtimes. Anypoint Runtime Fabric can be installed in your on-premises data center or cloud-hosted environment (Azure, AWS). This type of deployment is similar to that of CloudHub in that it offers high availability and has zero-downtime for data centers.
One of the key tasks of supporting a vital API program for your company is dealing with change over time. In previous articles, I’ve talked about the importance of managing the entire API lifecycle and how to recognize important milestones in the life of an API. These milestones often signal that a change in the way the API is treated, measured, and managed needs to change.
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.