Business has ideas; IT has the capabilities to launch them. Until now, when it came to API development, most enterprises leapt from ideation to build. They skipped the Design stage and went straight to Create. They also skipped millions of dollars in savings and countless development hours that could have been spent on user experience or business logic.
By enabling the enterprise to create a portfolio of pre-built core APIs abstracted from code and standardized to needs across lines of business, ignite helps businesses design API Products that share the important characteristics of great physical products like iPhones or Lexus sedans — products that are consistent, appealing, reliable and world class.
But Apple and Lexus don’t let engineers design phones and luxury sedans. Successful companies design an overall picture of what they want their product to do before they start manufacturing.
The average large enterprise needs about 400 APIs to transform their core business functions to digital experiences. It’s a mistake to place the burden of all of those APIs directly on developers without designing an overall vision of how those APIs should interact and help business innovate.
ignite’s planning functionality allows you to expose your enterprise’s API building blocks to anyone in the business who wants to innovate.
ignite Design phase equips you to design core functions for the business, not by use-case. With this broader design capability, you gain control and configurable, self-service governance. And you gain speed.
ignite allows you to design common microservice building blocks, with consistent resources from data and taxonomy models, standardized API definitions and system of record mapping, and change management with lineage and impact analysis. You can capture detailed information in the specification and expose reusable design artifacts, like your Items API — made up of consistent product ID, description, price, weight, and whatever else is critical to your business functions — to be used in every API that involves Items. You can design your Payment API comprised of standard payment and bill pay and wallet management and B2B pay code for any APIs in any line of business that requires payments.
Once you’re able to design and expose your API portfolio, you won’t need to duplicate these basic building-block units with every new API. ignite lets you design standardized paths and common flows, common logic and data and standard contracts across regions, across lines of business, and ready for development.
Designing a clearly visible API portfolio in ignite also helps enterprises prepare for agility in the face of emerging technologies. Today stores — or branches, agents, hospitals — use separate, siloed systems for many functions, such as inventory management, customer loyalty, and price comparisons with local rivals. Consolidating systems is much faster when you’ve captured the design details.
And with the rise of Big Data, analytics, and IoT, the eventual aim is to bring all of this information under one roof. Stakeholder systems (the system of record mapping to API definitions) will align to data in motion (the APIs, web services, and events) allowing you to assess and assimilate all of the company’s operations using analytics.