Why America’s Leading Mortgage Technology Provider Runs its Business on Apigee
3990
Of your peers have already read this article.
3:30 Minutes
The most insightful time you'll spend today!
Black Knight is a leading provider of technology, data, and analytics to the mortgage industry, catering to both large and mid-tier banks in the United States. Over the past few decades, we tended to manage customer integrations on a case-by-case basis. Whenever a bank needed to connect with a Black Knight app, we’d launch another integration project. Lather, rinse, repeat. Needless to say, this was inefficient; we knew we had to do something to centralize this process.
Building versus buying an API management platform
To start, we created some homegrown API solutions. Despite being largely successful with one of these solutions, we saw that technology advances were outpacing our capacity to update our solutions in-house. We knew we needed to move toward an API platform that would support RESTful architecture and that would fully enable mobile solutions. It also had to be extremely secure. Knowing how complicated such a platform would be to build ourselves, we decided that our developers were better off focusing on providing core solutions to Black Knight clients; engaging with an outside provider was the right way for us to advance our API strategy.
After a lengthy proof-of-concept process, we went into production with the Apigee API Management Platform from Google Cloud in 2018. In our opinion, Apigee was the most complete, robust, technically sound and full-featured option from among all of the API management tools we evaluated. Its ease of use was the deciding factor for our developers, and the Apigee analytics capabilities provided considerable insight into the anatomy of an API call—something the other platforms we considered didn’t do as well.
Choosing Apigee meant that we didn’t have to focus on developing and maintaining a tool or spend enormous amounts of money trying to keep up with security patching. For a large company like Black Knight, an API management tool is something we don’t want to spend a lot of time on. We know that Google Cloud devotes tremendous resources to it, and it would be difficult to replicate that in-house.
Black Knight has more than 150 client-facing applications. Almost half of them now are built with APIs that are externally facing, and many of these apps use APIs that integrated with other Black Knight applications. Add to that the huge number of applications out there that come from clients and third-party vendors, and suddenly, we had a management challenge from an API perspective.
Driving cultural change
We came to Apigee with the goal of containing and empowering our huge ecosystem of APIs, customers, third parties, and internal users.
Given Black Knight’s size, our developers and customers understandably each have different business goals, so getting everyone to come to a centralized platform is a great opportunity. My role is to help people consider other options so they can be open to the benefits that Apigee brings us.
Now that we’ve engaged with Apigee for over a year, we see two big benefits. First, the huge reduction in point-to-point integrations has produced tremendous efficiencies for us and our customers, who now get instant integration once they’ve been authorized for a particular API. Second, Apigee’s capacity for mobile enablement lets us satisfy our customers’ needs for secure mobile apps.
Simplifying security
From a technical perspective, security is complicated for mobile apps. We’re often accessing sensitive information on a mobile device that can’t always be trusted. This kind of scenario requires us to implement a number of security precautions to help ensure confidential information remains protected.
The Apigee API management platform addresses these needs in the simplest way possible. It solves complex problems related to security without having to deploy a new API proxy each time we need to support a particular mobile device upgrade. Our back-end applications remain protected because Apigee helps manage security, requests, access tokens, and authorizations. Today, our back-end applications work with Apigee to communicate with mobile devices or servers coming over the internet.
Apigee has also enabled us to do a better job sharing a variety of APIs. The developer portal lets us stitch together APIs and get more creative about how we can innovate and build new solutions based on these collections of APIs. At this point, anybody that has a nondisclosure agreement with us can register for the developer portal. The nature of our business is such that we can’t just open up our APIs to anybody, but it’s available to our contracted third parties.
Our Apigee journey has been exciting, and we’re making great progress. I’m looking forward to what innovations we will come up with next, thanks to the way Apigee enables us to create, implement, and deliver.
How PLAID’S Multi-cloud Approach with Anthos Clusters on AWS Drives Higher Business Growth
5443
Of your peers have already read this article.
3:00 Minutes
The most insightful time you'll spend today!
Editor’s note: Today’s post comes from Naohiko Takemura, Head of Engineering, and Kosukex Oya, Engineer, both from Japanese customer experience platform PLAID. The company runs its platform in a multicloud environment through Anthos clusters on AWS and shares more on its experiences and best practices.
At PLAID, our mission is to maximize the value of people through data, and we are developing a range of products that focus on improving customer experience. Our core product is a customer experience platform, KARTE, that can analyze the behavior and emotions of website visitors and application users, enabling businesses to deliver relevant communications in real time. We make KARTE available as a service to functions such as human resources and industries such as real estate and finance, and run the platform in a multicloud environment to achieve high-speed response and meet availability requirements. This is where Anthos comes in.
We introduced KARTE in 2015 and updated the system configuration in line with the addition of new functions and the need to increase scale. Our multicloud configuration is optimized through Anthos clusters on AWS, which give us access to the capabilities of Google Kubernetes Engine (GKE).
KARTE runs in two groups of server instances in each cloud; one group runs the management screens used by clients, and the other provides content for visitors to our website. In Google Cloud, the management system runs in GKE and content is delivered through Compute Engine.
We initially developed and operated the core of our services on another provider and from 2016 began to transition to Google Cloud due to its strong data processing capabilities. The products that handled big data, such as Cloud Bigtable and BigQuery, were attractive because they could handle data in real time and were compatible with KARTE. Now most functions, including peripheral aspects, run in Google Cloud, because we thought if we built a system centered on these products, it would become efficient to build other parts on Google Cloud.
While we considered migrating everything to Google Cloud, we decided to leverage its strengths alongside those of our existing provider, AWS. We felt a multicloud approach could create more opportunities and deliver higher growth than a mono-cloud environment.
We completed our move to a multicloud environment in 2017 and found that by building systems with almost the same content on two cloud services to leverage the strengths of each, we could reduce costs and improve performance and availability.
However, as KARTE grew, and the content of the service increased in complexity, we began to experience new problems. The increased load on the system due to an influx of in-house engineers from 2018 onwards impacted the scalability and development speeds of our conventional monolithic architecture running in virtual machines. We opted for an approach based on microservices and containerization, excluding the components that enabled real-time analysis as these had been modernized since initially being deployed in 2016, and the management screens, as the infrastructure running these did not require crisp tuning. Our key priority was to improve the ability of our engineers to deliver quickly.
From 2019, we turned to promoting microservices that make full use of container technology. When deciding to move from a target built on virtual machines to containerization, we evaluated the ease of use of GKE and decided to build in Google Cloud. At the same time, the number of systems with strict service level obligations was increasing, so to ensure higher availability, we considered running these in a multi cloud environment. The announcement of Anthos clusters on AWS at Google Cloud Next ‘19 in San Francisco provided an answer.
We had been wondering how to achieve the equivalent smooth operation of GKE in our AWS environment, and welcomed the Anthos clusters on AWS announcement. We consulted with a Google Cloud customer engineer through an early access program and quickly gained an opportunity to work with this version of Anthos. This allowed us to provide feedback and requests for improvement, and this paved the way for us to implement the product to take advantage of its functionality and future enhancements. With Google Cloud, we have been able to continue to interact closely with the development team to understand and provide input into the product roadmap.
We are now realizing the benefits of multicloud, including faster development speeds and higher availability. For businesses in general, we recommend they take a thoughtful approach to multicloud—while for us, multicloud is a useful mechanism that enables us to provide large-scale data analysis in real time, other businesses should consider whether multicloud is right for them and if so, the role of a technology like Anthos. They should also start small before ramping up. Moving forward, we are keen to see what other products Google Cloud is creating that can help drive our business to a higher level.
1108
Of your peers have already downloaded this article
4:30 Minutes
The most insightful time you'll spend today!
Learn about the benefits of a Google Cloud multicloud solution and how Google will partner with you to succeed, regardless of where your data resides or where your applications run.
3442
Of your peers have already watched this video.
51:50 Minutes
The most insightful time you'll spend today!
API Design Best Practices and Common Pitfalls
The job of an API is to make the application developer as successful as possible. When crafting APIs, the primary design principle should be to maximize application developer productivity and promote adoption.
API designers and developers generally understand the importance of adhering to design principles while implementing an interface. No one wants to design or implement a bad API! Even so, it’s sometimes tempting to look for shortcuts to reach those aggressive sprint timelines, get to the finish line, and deploy an API. The result? Not so desirable!
So what are the API design principles that help optimize developer productivity?
Watch Martin Nally explore the problems and solutions of quality API design. In this webcast , Nally shares insights on topics like designing quality APIs within the limitations of legacy software and recommendations on the technology choices that best satisfy the varying goals.
Nally is a Senior Software Engineer, Apigee for Google Cloud and has almost 40 years of experience as a software developer and architect and is an expert in web APIs. He currently designs and implements systems using APIs at Google.
Expert Takeaways on API Strategies from The State of API Economy 2021 Report
5745
Of your peers have already read this article.
8:00 Minutes
The most insightful time you'll spend today!
Did you know API traffic for Apigee customers increased 46% year-over-year, to 2.21 trillion calls, between 2019 and 2020? If you have more questions on APIs trends and their role in disrupting enterprises digitally, you can catch up on key take aways from the Google Cloud’s State of API Economy 2021 report and insights from Google’s experts on API-best practices.
APIs to Power the Future of Retail: Study Confirms
3554
Of your peers have already read this article.
1:30 Minutes
The most insightful time you'll spend today!
Today, retail customers have more digital-first, convenient ways of shopping than ever before. And APIs are one of the critical pieces of technology that have made this possible by giving retailers the ability to transform their systems and processes in an efficient and quick way.
APIs have allowed retailers to be more accessible to their remote customers with services such as order online and pick up in-store, curbside pickup, fulfilment of orders through delivery partners, and personalized recommendations while shopping online etc. These capabilities have been especially important over the last year, as the world has changed at a rapid pace. With many changes to customer interactions yet to come, APIs will continue to play a pivotal role in helping retailers to further personalize digital experiences and streamline their operations.
In Google Cloud’s State of API Economy 2021 report, 32% of organizations reported increasing their digital transformation investments, while 16% stated they would completely change their strategies to become digital-first companies. Moreover, by early 2021, online sales had already reached levels previously predicted for 2022, and APIs will become the foundation for business resilience and growth in retail over the next five years.
APIs are at the forefront of retail innovation
Retailers leverage APIs to experiment and connect teams for faster collaboration, helping them to use data for revolutionary experiences that increase customer engagement.
They allow retailers to innovate in new ways internally, externally, and across market borders. Modern digital experiences are built from a variety of data and functionality, throughout the entire supply chain, across multiple systems, and often belonging to a variety of services across distribution channels. APIs are the digital nervous system connecting everything together. They help retailers enhance internal efficiency, partner at scale, and leverage cutting-edge services such as machine learning—all because they make various kinds of technological value interoperable and easy for developers to access and reuse. In our research, 52% of retailers said APIs accelerate innovation by enabling partners to leverage digital assets at scale while 36% say they see APIs as strategic assets for creating business value.
Let’s take a look at some retail use cases and real world examples that are powered by APIs.
Deliver personalized customer experiences
Retailers are using APIs to create interactive and predictive personalized experiences.These range from “magic” mirrors that reflect personalized clothing, accessory, and even makeup suggestions; to smartphone alerts that encourage shoppers to check out special items while they’re browsing in the store; offers of coupons; and more. Behind the scenes APIs interconnect between the store and consumer data, business intelligence, and application security to bring these innovative experiences to life.
Streamline retail operations
APIs can help any retail business to operate more efficiently, from human resources, customer service, and distribution, to invoicing, marketing, and compliance. For example, APIs make it super easy and simple to onboard, manage and train employees and contractors. They can help connect various internal and external third-party systems for use cases like tracking real-time package status and gathering consumer shopping insights.
Conrad Electronic, German retailer of electronic products, demonstrates how API management can lead to enhanced efficiency. They used Apigee to build a tool that provides store employees and visitors with product, service, and warranty information on their mobile devices. The company was able to not only use data to enhance offers and services to their customers, but also streamline operations because more than 60% of their customers were using the API-enabled tool.
Power the future of retail with APIs
APIs are key to driving innovation across all areas of retail. They are enabling retailers to not only implement continuous digital transformation but also develop tools that navigate disruptions as they occur.
Retailers are already harnessing the power of APIs to prepare for:
- Borderless channels across markets that allow for the free flow of products and shopping experiences in the way consumers want them.
- Interactive and intelligent merchandising that evolves in realtime to predict consumer needs and bolsters buying decisions.
- Autonomous and virtual shopping experiences that develop deeper consumer interactions and product insights.
To learn more about how APIs can help drive innovation, download our latest eBook. In this eBook, you’ll find more retail-specific API use cases, detailed real world examples and insights into how APIs are shaping the future of retail.
Manage APIs effectively
As you grow your API program, and start powering business-critical applications and front-end experiences with APIs, you need an effective way to manage and scale them. This is where Google Cloud’s Apigee API management platform can help. Top retailers across the globe use Apigee to gain control over and insights into their APIs and enables them to manage end-to-end API lifecycle. Click here to learn more about Apigee.
More Relevant Stories for Your Company
How Experian Transformed its Business by Using APIs
Chances are, when you think of Experian you think of a traditional credit bureau that provides credit reports. But Experian has transformed into a true technology and software provider. We gather, analyze, and process data in ways that other companies just can’t. Businesses use this data to make smarter decisions about credit
Are You Providing Sufficient Digital Leadership?
It has been seven years since Marc Andreesen’s famous article “Why Software is Eating the World” was published in the Wall Street Journal, and given the slow pace of change in many companies, some executives still may not be taking the threat of being “eaten” seriously enough. Software, and platform
Google Cloud Offering a Natural Migration Path for Developers Accustomed to Heroku
Modern developers worldwide have grown accustomed to the comfort of writing code, pushing to a remote Git repository and having that code be deployed at an accessible URL without having to worry about how it is deployed. This was a workflow popularized by Heroku years ago which brought joy and
Introduction to Cloud Shell Editor
Watch the video to understand how Google's Cloud Shell Editor and its powerful features-packed environment can streamline your development workflows.
