In the first article in this series, RESTful API Modeling Language 101, we saw how to design basic RAML and we had banking API as a use case. Here we will walk through some of the advanced RESTful API Modeling Language (RAML) to achieve code reusability and better code readability.
As any data manager knows, the influx of available data isn’t always necessary for business needs. That’s why event-driven architecture (EDA) is useful to help filter data that meets certain criteria, reducing the load on integration systems. EDA enables different systems to work with different data through loose coupling between microservices.
In the first blog post of this series, we described how Anypoint DataGraph relates to API-led connectivity. In the second post, we presented three approaches on how to consume APIs:
There are several steps that go into updating a CloudHub-hosted runtime engine, including security updates and data patching that are applied directly to the runtime engine. When it comes to patch and minor version updates, these must be applied to the runtimes by the application owner. These updates require regression testing of the applications, but […]
This is the second blog in a three-part series on how APIs can be used to maximize the value of data in a digital organization. Part one examined the economic properties of data, and principles of how digital organizations should treat data.
Nearly every company today is making strides toward agility — and being agile often requires organizations to not only act fast, but act in real time. This is only possible with fast, real-time streaming of data, leveraging microservices built based on an event-driven architecture.
Anypoint Connectors provide a connection between a Mule flow and an external system — such as any source of content, database, protocol, or API. While there are thousands of out-of-the-box connectors in Exchange, sometimes you need a custom connector to meet your specific needs.
Several of the development teams that I work with often run into the same problem: each developer has their own method of deploying Mule applications. This can create a significant amount of confusion and can lead to broken applications. Without a standard deployment process, additional time is spent on alignment or fixing broken applications as […]
Mary Joy Sabal, MuleSoft Practice Lead at Datacom, is a multi-MuleSoft Certified Developer and Architect and MuleSoft Ambassadress. She frequently speaks at Meetups and is the Wellington Meetup group leader.
As technology rapidly evolves alongside customer expectations, adopting an API-first approach in payments has become critical. APIs are the building blocks of the next-generation of payments platforms, utilizing the power of Anypoint Platform.