In today’s connected world, immense amounts of data is being created at a rapid pace. Forward-thinking businesses are continually seeking ways to enhance their technology to improve efficiency, streamline operations, and provide superior customer experiences. A critical aspect of achieving these objectives lies in the effective use of Application Programming Interfaces (APIs).
In 2002, Jeff Bezos famously issued the Amazon API Mandate, outlining 6 rules that helped Amazon and AWS become the behemoths they are today.
Jeff Bezos
- All teams will henceforth expose their data and functionality through service interfaces.
- Teams must communicate with each other through these interfaces.
- There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.
- It doesn’t matter what technology they use. HTTP, Corba, Pubsub, custom protocols — doesn’t matter. Bezos doesn’t care.
- All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.
- Anyone who doesn’t do this will be fired.
20+ years later, the API-led development movement is stronger than ever, and businesses in many industries are reaping the benefits. This case study explores how a comprehensive API strategy, focusing on System, Process, and Experience layers, facilitated a major insurance brokerage firm’s transition to a more agile, data-driven organization.
Background
The insurance brokerage firm embarked on a journey to modernize its data architecture to support its expansive service offerings. The company’s goal was to leverage its vast data resources more effectively, enabling better decision-making and enhancing customer interactions. Central to this initiative was the adoption of a layered API strategy, distinguishing between System, Process, and Experience APIs.
The Challenge
The company faced several challenges in its existing architecture:
- Data Silos: Critical business data was scattered across various systems, making it difficult to access and synchronize information effectively.
- Scalability Issues: The existing infrastructure could not efficiently scale to meet the demands of the company’s growth and the pace of technological advancement.
- Integration Complexity: The integration of new services and applications into the existing infrastructure was complex and time-consuming.
- Inconsistent User Experience: There was a lack of consistency in the user experience across different applications due to varied data access methods.
Strategy Implementation
To address these challenges, 27Global and the company implemented a three-tiered API architecture comprising System, Process, and Experience layers. Each layer played a pivotal role in transforming the company’s approach to data management and service delivery.
System APIs
At the foundation, System APIs provided low-level access to core systems of record, such as data lakes, data warehouses, external systems, and when necessary, master and transactional databases. These APIs ensured secure and standardized access to raw data without exposing the complexities of the underlying systems.
Process APIs
Building upon the System APIs, Process APIs served to orchestrate and refine data for specific business purposes. These APIs facilitated complex operations such as aggregating data from multiple System APIs, transforming data formats, and enforcing business rules. They effectively acted as the backbone of the company’s business processes, enabling functionalities like client management, invoice processing, and policy handling through well-defined service endpoints.
Experience APIs
At the top of the architecture, Experience APIs were tailored to deliver data and services in formats optimized for specific user interfaces, whether they be mobile apps, web applications, or third-party integrations. By abstracting the business logic and processes, Experience APIs ensured a consistent and seamless user experience across all digital touchpoints.
Outcomes
The implementation of this layered API strategy yielded significant benefits:
- Enhanced Agility: The company could rapidly integrate new services and data sources, significantly reducing the time-to-market for new features and capabilities.
- Improved Data Accessibility: With standardized APIs, the company unlocked siloed data, making it readily available across the organization for informed decision-making.
- Scalability: The modular architecture allowed for the easy scaling of services to accommodate growth and adapt to changing business needs.
- Consistent User Experience: Experience APIs enabled uniform data presentation across various platforms, enhancing overall customer satisfaction.
The strategic implementation of System, Process, and Experience APIs transformed the company’s approach to data management and service delivery. By breaking down data silos, simplifying integration, and enabling scalability, the company positioned itself for future growth and innovation.
As 27Global’s VP for Client Service, Patrick Kinne ensures we deliver for our clients, continuously refining and advancing our processes, and streamlining and extending our solutions to fit the market. Pat is based out of Denver, works with clients coast to coast, and leads a globally distributed delivery team. He is grateful to work with some of the best in the business to solve challenging and interesting problems every day.
