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,
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.
This is the question that many of us are faced with when starting with APIs, and quite invariably, there would be either of two broad scenarios that we generally find ourselves in. We are either starting green field under the clear blue sky with every little thing to elicit, introspect, and design; or else we are in a continuum, trying to understand the current system,
Picking up from the second part of this series, this blog post will wrap up building an end-to-end API solution. For the first post, you abstracted source systems with APIs to add flexibility, ease of consumption, and increase adoption and integration possibilities.
Here at MuleSoft, we talk a lot about how API-led connectivity can speed up your development cycles, and I’m here to guide you through how to do it. The API-led approach is a natural evolution from developing libraries, writing digestible markdown files, and sharing them on GitHub.
Update 10/23/2017 from the training team: In the light of your feedback on how much you love this certification, we’ve elected to not retire this certification and, instead, release the MCD – API Design Associate (RAML 1.0) as a non-proctored certification exam. You’ll be able to take it as a stand-alone exam, or using the voucher that comes with the Anypoint Platform: API Design course. Thanks for letting us hear from you!
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.