The ignite platform uniquely sits upstream of CI/CD in the API and Lifecycle. Abstraction and integrations are used to ensure ignite delivers a Holistic API and Service Catalog with Extended Lifecycle that’s seamless with your existing architecture, and delivers reliable and reusable APIs and Services for everyone.
With abstraction, your APIs and Services are brought into a common metadata framework and organized into Designs and Specifications. This provides a pure abstracted view (away from all code and implementation details) for non-technical users to discover, understand, and use the APIs and Services in your catalog. There is also a semi-abstracted technical view (with all the technical details for the Services, including payloads, NFRs, policies etc.) and these can be used to generate any code base for downstream targets using output templates.
Bi-directional integrations with CI/CD and runtime systems enable your APIs and Services to be deployed directly to their targets, with deployment history available directly in ignite. What’s more, ignite’s own APIs can be used to configure integrations with almost any other system, including upstream domain driven design and product tooling.
This video will take you through how ignite’s functionality supports abstraction and integrations as two key aspects of a Holistic Catalog with Extended Lifecycle.
00:00 - 0:46 Why abstract your Services into a common metadata framework?
0:46 - 1:54 Designs and Specifications: abstracted views and technical details for your Services
1:54 - 2:18 ignite sits upstream of CI/CD and enables Services to be built directly in ignite or imported in
2:18 - 2:38 Finding existing Services using the taxonomy tree
2:38 - 3:24 ignite integration to CI/CD methodology
3:24 - 3:38 ignite’s out-of-the-box integration targets
3:38 - 4:17 ignite’s own APIs can be used to establish integrations with many more downstream systems
4:17 - 5:30 Integrations at the Design and Product Bundle level
5:30 - 6:17 What are output templates and how do they work?
6:17 - 7:02 Benefits of using ignite’s abstraction and integration for your organization
For more on API abstraction, check out our API abstraction blog post.