ignite - Run | digitalML

Run

(Connect+) ignite is the only technology available that extends through the entire lifecycle of API Product Management. We help the world's largest organizations Plan, Design, and Build APIs for all of their Runtime environments, acting as lifecycle, catalog, and highiest end-to-end view of your digital story. Meaning runtime is no longer hold-your-breath time.
Give business and product owners a holistic view of all of your existing and in-flight APIs, and allow business and IT to collaborate and manage the intake and prioritization of new innovative ideas and projects.
Design and expose your catalog of 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.
Auto-generate contracts, code, mappings between layers and transaction, and test conditions so developers can easily assemble repeatable, predictable and rapidly scalable API products, then plug specific functionalities into the back-end as needed. This frees up IT minds to focus on business logic, implementation, user experience, back-end connections and all the big-brain thinking that optimizes their skill sets.
API Products planned, designed, and built in ignite are ready to be delivered to run, extending consistency, lineage and speed to production and execution. Once in run, ignite provides a window on actual KPIs and ROI, letting the business know how API Products are actually performing in the market and providing accurate investment decisions.
API Products planned, designed, and built in ignite are ready to be delivered to the Run phase, extending consistency, lineage, speed to production, and execution. Once in Run, ignite provides a window on actual KPIs and ROI, letting the business know how API Products are actually performing in the market and providing accurate investment decisions.
Vendor-Agnostic
Authoring APIs
Testing Environment
DevOps Dashboard
ESB integration
SCM integration

We don’t just do runtime, we drive it.

Design-driven development means one system of record, for all of your abstracted services. So you can generate an API, microservice, event, message, or all of the above from your original design template directly to your multiple runtime environments.

Because the enterprise API strategy must be equipped to scale.





To scale an enterprise API program, Plan, Design, and Build should drive Runtime... and not the other way around.


Critical Capabilities of ignite versus typical runtime API manager

“DigitalML chose to come at API Management from the Design side. Others have come at it from the runtime. While digitalML is adding features rapidly to their runtime capabilities, consider what is more important to you to begin with - the proper design, flexibility, data lineage OR runtime criteria such as lookup, metrics etc. That will inform you well during platform/tool selection. API Mgmt, if done properly, spreads like wildfire inside an organization.”

- 5-Star Gartner Customer Review





Where ignite fits into your lifecycle...


How ignite supports the Plan, Design, and Build parts of your API management lifecycle, plugging into any and multiple runtime environments.



By abstracting API development and handing over repeatable, predictable, and scalable APIs for implementation, ignite makes it easier for you to take advantage of big changes seamlessly.

Use Case





For example, retailers have recently been rolling out Buy Online, Pick Up in Store capabilities. Banks have introduced a service that allows users to take a photo of a check for instant digital deposit. These are quality digital experiences for the end-user. They take 10 to 12 core APIs to run. And that information allows the business to continue innovating and scaling at speed. But the business - and your customers & competitors - have more ideas.

With ignite, by the time you’re making runtime decisions, runtime environment technology is no longer a decisive factor. Maybe, like many enterprises, you bet big on closed systems through a single vendor and now you want to transition to an open-source environment. When you use ignite, you have vendor agnostic design artifacts in place. You have a view of what’s in production, whats in flight, what’s been requested and whats been delivered. Because all of that is stored and captured, you can quickly reconcile and generate your API Catalog and point it from one runtime system to another.

Resources