The SOA program contained an enterprise integration layer that was appropriate for back-end integrations. However, Colruyt knew an uprise in front-end applications like the Collect&Go mobile app. That’s when Colruyt decided to team up with Archers for the implementation of an API program. A new strategic project was introduced: mobile readiness, enabling Colruyt to meet the challenges of these new channels.
Colruyt started with the creation of internal APIs but the end goal was to prepare the organization for the use of all kinds of APIs, like public and partner APIs. With this new strategy in mind, a new front-end integration layer was introduced. With this new focus, new requirements arose.
As the actual enterprise integration platform was not able to meet the requirements of API management, Colruyt decided to introduce a new platform with a focus on API management. After setting up this platform, governance entered the picture. To meet these governance challenges, Colruyt had to evaluate their API lifecycle in which activities and deliverables were defined. This governance process contained several quality checkpoints, linked to the application lifecycle. However, this governance was still not meeting all requirements for API management, as Colruyt aimed at a fast market intro and fast delivery. To meet these goals, Colruyt diversified service governance by service type and focus:
- The full governance applied to core SOA services and is a completely centralized governance;
- Light governance applied to reusable APIs and is a partially decentralized governance (architecture and identification are still centralized, but design, quality and certified checkpoints are decentralized);
- No governance APIs are completely decentralized governance.
As Colruyt aimed for faster delivery, they also worked on open API specifications. These were uploaded to the development API gateway where necessities like security could be added.