System APIs ownership and governance model
In assigning ownership of System APIs, one should consider the near and long term goals for the shared System API.
Leveraging APIs to drive better patient outcomes
At MuleSoft’s booth on the 2019 HIMSS exhibit floor, Bits in Glass showcased real-time syncing of blood pressure data between medical devices.
Getting on track with microservices
As enterprise IT seeks greater speed and agility through the adoption of a microservice architecture, they find this new paradigm can collide with long-established operating models.
Modernize life sciences with an API infrastructure
Life science IT departments face increasing demands because of clinical trials’ growing complexities, including the proliferation of specialized applications, ballooning numbers of stakeholders, and data security and privacy considerations.
How should banks tackle the innovation challenge from fintech startups?
The influence of rapidly-evolving macro-economic conditions and regulatory changes, especially following the 2008 financial crisis, have always kept the financial services industry on its toes. However, few could have foreseen the impact created by the waves of new fintech startups that have surged into the market in recent years. The charge is being led by innovative new entrants, such as Atom Bank, TransferWise and Sonovate, which are finding success in using new technologies to deliver traditional financial services in ways that revolutionise the customer experience.
5 reasons why ESB-led integration is out and API-led integration is in
Integration has been an enterprise challenge for a long time. In order to create the new products, applications, and services that businesses need to confront the digital revolution, you have to connect systems, data, and devices. There’s no way around it. Enterprises struggled with point-to-point integrations, which created a spaghetti-like mess of code, and then, for many years, companies found a better integration solution with ESBs (Enterprise Service Bus) and an ESB integration approach.
Dev Guide: Build a Mule integration with a Slack slash command (Part 3)
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.
Dev Guide: How to Design a Process API (Part 2)
Before we get started with this blog, if you haven’t checked out Part 1 of this Dev Guide series, make sure you work through that first, where we went through developing a resilient, governable, and flexible API layer on top of your source systems—what we call system APIs.
Report: Over 50% of Consumers Receive a Disconnected Experience from Insurers
Today, more than ever, insurers are at risk. According to the Connected Consumer Report, more than half (55%) of UK consumers believe that insurance companies provide a disconnected experience across online and offline channels; and 63% of consumers would change their insurance provider if insurers do not address this disconnected experience.
Reusable KPIs for Reusable APIs: The Metrics – Part 2
In part 1 of this post, we have established the overall value proposition of defining reusable KPIs in an attempt to assess and drive the concept of reuse within your API platform. Once the capability to establish and monitor both abstract baselines and progress against them have been established within an enterprise, the next step is to determine what metrics are worth tracking, where they break down, and how they relate to each other.