Integration is critical for all businesses, and the right Integration Platform-as-a-Service (iPaaS) is a key piece for any organization looking to accelerate digital efforts. However, truly unlocking your data and systems is about more than just connecting systems and applications. To build an agile and future-proof business, you need an integration strategy and partner that recognizes that iPaaS alone isn’t the end solution.
Chances are that if you found your way to this blog — you already understand the importance of integration within the enterprise. According to the 2020 Connectivity benchmark report, the average organization has 900 applications and only 28% of them are currently integrated.
A common misconception is that organizations either need an integration platform as a service (iPaaS) or an API management solution to solve their integration challenges — however,
The demand for flexible business models from our consumers is at an all-time high, re-assembling and re-composing organization’s digital products at a faster pace is the top priority of stakeholders. Purchased off-the-shelf applications are not fluid enough to keep pace, an application layer that provides active personalization of business capabilities is required to satisfy expectations from customers — and is key to making the composable enterprise dream a reality.
Take it from a serial consultant that helps organizations in their composable enterprise journey — we have learned that the challenges ahead are real.
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.
Like any product, APIs and client apps that use APIs have their own lifecycles. They each experience their own Create, Publish, Realize, Maintain, and Retire phases. When things go well, services will experience important use (and re-use) and grow to maturity to provide significant contributions to your company’s performance. And client apps will use APIs that connect to one or more services and, in their own way, create their own cycle of growth and maturity to increase revenue and/or customer use in ways that also spells success for your organization.
Just like any product, APIs have their own lifecycle with distinct phases. And recognizing them means you can take advantage of them by focusing on the right aims and the proper convenance at each step along the way. This was one of the key lessons we focused on when we wrote the “Continuous API Management” book in 2018.
There are situations when you need to invest lots of time and effort to get an API product ready for consumption.
O’Reilly Media published its first book on API management in December of last year. I sat down with the book’s authors to explore some of the core concepts of the book.
In 1989, when Jan Carlzon, the now former CEO of Scandinavian Airlines (SAS), published his book Moments of Truth, he posited that a customer’s journey with any organization involves an untold number of seminal moments, each of which possesses the power to make or break that company’s future with that customer. Yet, somehow, long after his book was published, if you ask anyone who regularly travels by air about their experiences,
APIs are becoming critical to thriving in today’s digital economy. In our recent Connectivity Benchmark Report, we surveyed over 650 IT leaders and found that businesses across industries are realizing great benefits from APIs. This includes increased productivity (58%), increased innovation (48%), and increased employee engagement (43%).
For many, a continuous integration (CI) and continuous deployment (CD) pipeline is an important aspect of software development that provides wide benefits––from reducing error-prone deployment work to providing early visibility into bugs. This blog post will cover the API lifecycle through different phases––from designing and managing APIs to deploying and discovering them. The blog will provide a step-by-step guide for implementation and configuration using Anypoint Platform, including:
