Our recent CIO survey with Oxford Economics contained a few takeaways that stood out to me: most companies are using API-first strategies, and those most committed to this concept report faster innovation and greater value from business partnerships. Even so, the survey indicates that a healthy minority of enterprises still think of APIs in integration-first terms.
Over the last several years, as digital services and interfaces have become the primary way businesses interact with their customers, maintaining ‘business as usual’ has demanded digital transformation. In difficult times such as these, however, it may be tempting to put digital transformation projects on pause until budget surpluses return. This is a mistake.
APIs are a critical component of any enterprise’s digital transformation strategy. They can drive customer engagement, accelerate time to market of new services, power innovation and unlock new business opportunities. Therefore, choosing the right API management platform is critical to running a successful API program, and research from industry analyst firms like Forrester Research can help enterprises evaluate and choose the right solution.
Worldwide, businesses are adapting to the new market conditions by transforming their current operating models to meet the new consumer demands and improve productivity, all while still focusing on achieving growth. In this new era, taking an outside-in approach to digital business ecosystems can help organizations harness their existing resources and relationships to drive new innovations and efficiency.
Among forward-looking software developers, Envoy has become ubiquitous as a high-performance pluggable proxy, providing improved networking and observability capability for increased services traffic. Built on the learnings of HAProxy and nginx, Envoy is now an official Cloud Native Computing Foundation project, and has many fans—including among users of our Apigee API management platform.
As most software developers no doubt know, there are two primary models for API design: RPC and REST. Regardless of model, most modern APIs are implemented by mapping them in one way or another to the same HTTP protocol. It has also become common for RPC API designs to adopt one or two ideas from HTTP while staying within the RPC model, which has increased the range of choices that an API designer faces. This post tries to explain the choices, and give guidance on how to choose between them.
For more than 70 years, EBSCO has supported research at private and public institutions, including libraries, universities, hospitals, and government organizations. One of the reasons that customers have continued to rely upon us over the decades is because we actively innovate and adapt new technologies to give customers access to the growing pool of digital resources in the information age.
Editor's note: Today we hear from Brad Plothow and Mihir Sambhus from Womply, a software-as-a-service company that makes CRM, email marketing, and reputation management software for small businesses. The company recently developed APIs to help small businesses use data to gain a clearer picture of their markets—and how to compete in them.
Based in Dubai, Emaar is a real-estate development company operating across a number of verticals, including properties, shopping malls, hospitality, and entertainment. Learn how Emaar develops new customer experiences using APIs. Emaar is known worldwide for our luxurious properties and communities. Our most well-known property is likely the Burj Khalifa, which is the tallest structure in the world at 829 meters.
Editor's note: Today’s post comes from Surin Asawachaisittigul, head of open APIs at Krungsri Consumer a subsidiary of Krungsri Bank, the fifth largest bank in Thailand, and focuses on personal loan and credit card services. Using APIs, Krungsri Consumer is taking an established bank into the digital future of finance. The finance industry is changing quickly in the digital age. Customers no longer want to pay for purchases in cash.
