In our previous blogs, we covered a high-level overview of various Anypoint B2B integration solutions to seamlessly connect with your trading partner ecosystem for exchanging business transactions. As part of the “How to” blog series, we will walk through various B2B integration use cases with Anypoint B2B Solutions. Our goal with this blog is to cover a use case that implements secured connectivity leveraging Anypoint AS2 connector to send and receive B2B transactions.
I am happy to announce our new release of Anypoint Studio 7.7 is now available. Our goal with every new Anypoint Studio release is to further improve and streamline the API and integration development process for our MuleSoft devs. This means making it faster to build, with more powerful and more intuitive tooling. This release includes a new perspective for inspecting input and output payloads when using DataWeave, the ability to natively create API specifications in Studio,
Have you ever struggled with opening multiple windows in API Designer as you write your API specification or tediously renamed a symbol by hand in multiple spots of your RAML file? Well, worry no more — API Designer has solved these issues for our developers, making API specification development easier than ever. Introducing API Designer multi-tabbing and rename symbol capabilities! Below I’ll dive into what improvements we’ve made to these features:
Every day, businesses are working toward becoming a ‘digital’ enterprise — but what does it mean to become digital?
Digital design is far more than simply putting your business online; it is changing the people, process, and technology operations of an organization. Thus the term ‘digital transformation’ was coined to show that this is a change in company strategy and not just a simple project. Organizations completely transform the way they operate.
When surfacing data from systems of record, one of the concerns designers and developers need to address is the potential of retrieving an enormous number of results in a single load session. This requires significant processing power on both the client and server sides and network traffic, and can degrade the overall data consumption and experience.
There are different approaches to address this concern, but one of the most widely used is the concept of pagination.
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.
In the previous blog entry, I described two specific design artifacts (user types and personas) that can be used to inform an intentional API consumer experience. In this entry, we’ll go one step further into the API ecosystem and map out how the consuming developers (i.e., the direct users of the API) work with other user types to achieve their goals. Understanding how all the players come together to support your API consumers is fundamental to developing the right API product as well as the right set of services and support offerings to make your users successful.
In this episode, Mike and Matt are joined by special guest Stephen Fishman, Regional Vice President of Customer Success Architecture at MuleSoft and longtime API product expert. Stephen shares insights on product-oriented approaches to API design, development, and lifecycle management. Topics range from API discoverability to launch strategies to a relentless focus on API consumers. Have a listen here:
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,
API creation and adoption are having a moment. As of January 2018, there are nearly 19,000 public APIs in ProgrammableWeb’s API directory. According to recent research, 94% of companies say they either have or are developing an API strategy. APIs are seen as an enterprise necessity.
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.