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.
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.
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.
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.
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.
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.
A lot of enterprise IT concepts and tools have experienced dramatic change in the last decade. Several long-lived rules of thumb have faded into irrelevance. However, one conceptual holy grail has survived the volatility of the IT transformation toward all things cloud, DevOps, and APIs: reuse. Like historical explorers seeking the Northwest Passage, enterprise IT executives have long sought out ways (e.g. SOA) to drive down the cost of solution development through code reuse.
Networks have always been at the heart of our society, defining our relationships, creating our experiences and ultimately shaping our lives. From the steam railways that enabled commerce between cities and towns, to the cables that paved the way for global communication over telephones and then the internet, networks have a history of redefining our way of life.
More recently, the internet has given rise to virtual networks that allow us to connect to vast computing resources,
In my role at MuleSoft, I advise federal agencies and commercial businesses in connecting their applications, data, and devices. Those conversations center around building modern Application Programming Interfaces (APIs) to create new capabilities. A modern API is one that enables systems to exchange information securely using broadly adopted standards like REST and JSON.
These days there are APIs for nearly everything, like an API for your thermostat. I can change the temperature in my house from my phone or my smartwatch using an application that interacts with my thermostat’s API.
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.