Enabling roles across both Business and IT when it comes to API and Service Development is key for:
- Ensuring speed and scale, while delivering reliable, reusable, and well-governed APIs and Services
- Achieving digital maturity where multiple roles across the enterprise are providing and consuming APIs
The ignite platform supports two approaches to this role enablement – top-down and bottom-up API development.
Top-down development involves a domain driven design/product-driven approach to API design and development, and utilizes the enforcement of API standards through governance compliance checks, and encouragement of reuse of common data elements, so that service documentation is normalized and consistent for your developers.
In bottom-up development, you’re allowing your development team to work in the tools and environment they’re familiar with, while also allowing, through integration and import of the raw service documentation, developers to contribute to populating your Holistic Catalog.
This video demonstrates how the ignite platform supports both these approaches simultaneously, and provides flexibility for you to move to a more top-down development approach over time.
00:00 - 0:47 What do we mean by top-down and bottom-up role enablement?
Top-down enablement and API development
0:47 - 1:17 Browsing information models in ignite
1:17 - 1:48 Creating a new Service in ignite
1:48 - 2:34 Adding reusable data elements to a Service
2:34 - 3:22 Governance checks and OpenAPI validation, and extensive Service metadata
3:22 - 4:25 Classifying objects using taxonomy models
4:25 - 5:11 Approving Services for reuse
Bottom-up enablement and API development
5:11 - 5:42 Importing a new Service version into an existing Design from a JSON file
5:42 - 6:05 Prompting enhanced metadata for Services built outside ignite
6:05 - 6:30 Creating a new Design and Specification from a JSON file
6:30 - 7:09 Consoliating data elements to create a data model over time
For more on role enablement strategy, check out our API development blog post.