Unifying three brands with a powerful API backbone
Based on an initial study, the following areas needed to be addressed on priority:
- Complex legacy architecture with multiple integration points in each brand
- No uniformity in the products used and back-end application stacks - from billing and mediation to CRM.
- No single sign-on capability to access related functionality
The overall architecture with multiple interfaces serving customers in each brand:
THBS rolled out an API Strategy along with the customer stakeholders in a phased manner. A governance board was set-up to monitor the identify-create-reuse-retire cycle for APIs based on the functionality they offered and their reuse potential in the new setup. The governance board also put in place processes needed to enforce discipline across the design-build-test-document API lifecycle phases to succeed with the initiative.
The current architecture is the result of a successful strategy and robust governance: