For close to twenty years, the “common standard” of APIs on the web has been summed up in one word: “RESTful.” Designers, developers, and software architects have promoted, debated, and derided the notion of RESTful APIs in successive waves over the years with all sorts of pundits declaring REST “dead” and offering some other current practice as “the new REST” or, even better, “the REST killer.” Probably my favorite rejoinder in this space is Matt McLarty’s “
API management is the process of designing, publishing, documenting, and analyzing APIs in a secure environment. It provides users — like developers and partners — the ability to access an API, governed by a set of configurable policies.
In this post, we will take a closer look at the benefits of using the basic endpoint approach to deploy a packaged API implementation along with a proxy as a self-contained application and examine the required steps for the API pairing within API Manager using the API autodiscovery concept.
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.
Statue in Kipling, Saskatchewan, Canada commemorating the red paperclip that Kyle MacDonald used to start a series of trades that led to him obtaining a house in that town.
In a previous blog post, I explained how Clayton Christensen’s “jobs to be done” theory can be used to identify innovation opportunities that are enabled by API products. The CURE methodology from that blog post is the basis for the group exercise in the API Strategy Workshops we deliver worldwide.
I’ve recently been in touch with a friend who is a lead architect at a large-scale distribution company to understand how COVID-19 has impacted their business and what they are doing to ensure business continuity. Suddenly the global coronavirus pandemic has upended how companies operate and respond to changing consumer behavior and shocks to the supply chain. Companies need to adapt by enhancing their digital capabilities and transforming IT operations to be more responsive,
Modern supply chain management solutions often rely on both EDI and APIs. EDI is often seen as the business standard for B2B transactions, however, the use of APIs has become more prevalent, especially for real-time data transfer. Businesses aren’t forced to choose between using modern APIs over traditional EDI, as there are uses for both in B2B integrations. As businesses digitally transform, they must adopt a balanced strategy for B2B integrations by embracing real-time transactions via APIs to augment their batch transactions via EDI.
Asynchronous messaging is critical to creating a truly scalable system, where various services can communicate with each other easily, can scale up and down independently, and where one service failing won’t cause all the other services to fail. With the trend of microservices in full swing, this has become even more important. As Tim Bray from Amazon stated: “The proportion of services I work on where queues are absolutely necessary rounds to 100%.”
More than a decade on, the API economy continues to boom. As digital transformation sweeps organizations of every size in every industry and API-enabled digital channels like smart home devices become mainstream, the importance of APIs in people’s everyday lives is only increasing. However, just as the original gold rush that ballooned the population and wealth of San Francisco had devastating consequences for California’s original inhabitants, the 21st-century digital gold rush for which Silicon Valley stakes a major claim also has its collateral damage.
Are you stuck with business as usual where you end up building solutions with a platform as a service (PaaS) for project needs? Do you want to get out of always being reactive, creating further technical debt and never able to execute the vision of building rapid solutions that would end up being assets to your organization? This is my story of how I reduced IT costs and the increased project quality at a large beverage company.
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.