Enterprise-Wide Dashboard Reporting
Isn't it time you got the full end-to-end story on your digital products?
The modern enterprise IT department is a dizzyingly complex landscape, and it makes reporting in full quite a challenge. Companies tend to adopt multiple environments and add new technologies as they come to market. The variety of cloud products and open-source innovation allows IT to try on vendors and configurations as they see fit. To truly capitalize on the cloud's capability to stand up multiple containers in mere seconds, you need core business APIs that are reliable, reusable, and quick to deploy from idea to delivery across all configurations. And you need to know exactly how every service is performing, and which to scale.
From Reporting to Scale
The visibility ignite offers makes adapting APIs faster and more efficient. Business wants to keep innovating. They want to keep offering new services — dozens more — as they spot the need and opportunity. By investing in the Plan, Design, Build, Run lifecycle, enterprises accumulate the technological agility that core building blocks provide — but also the innovative insights to see where the next opportunity lies and how to quickly capitalize on it. The information ignite streams into the Run phase is far more robust than what is possible by building ad hoc product by use-case.
There are 2 parts to runtime within ignite.
1. API Management
With ignite, you've designed your services and have generated implementation detail that can include policies and business logic, and now you want to manage that API, covering things like which consumers have access, security, and other proxying details. ignite supplies those functionalities with bundled open-source solutions (Kong and Kubernetes), so that you can test APIs in an affordable environment, take advantage of our detailed design-first reporting to get the full story, see what's performing best, and prioritize/scale up accordingly.
For example, if you wanted to make a change to a service in production -- let's say you want to scale back on transactions per second on an API. You can return to the design stage, make an edit to the throttling and other NFRs so the service doesn't shut down, and push it out directly through management into the execution and its running environments.
2. API Execution & Reporting
ignite also ships with open source execution (Kubernetes) or integrates with your own runtime deploy and/or execution (e.g. Apigee, APIC, Kafka) to to ensure the APIs perform within the terms set in their Service Level Agreement(SLA), as well as monitoring the health of the APIs and container scaling. Many customers use this option to consolidate the monitoring and stack it up against the original design details, all of which are readily kept within the service. So if you go to the service summary page, you're able to see the performance monitoring, and what it was originally designed for, the actual results stacked up against the expected.
ignite naturally links between Build and Run, but it also features a unique link-back between the Run and Plan phases. In Plan, ignite asks API owners to project KPIs and estimate ROI. In Run, our platform provides a window on actual KPIs and ROI, letting business know how the products are actually performing in the market so that they quickly know which products to scale. ignite provides full API lifecycle management.
ignite also allows the business to project what a change in the Plan or Design phase will mean in the Run phase — and, conversely, because you’re using the same building blocks for each API product, how a change in Run conditions can influence Plan and Design for subsequent iterations.
Ready for the Future
Enterprises that want to optimize agility must develop API products that are immediately adaptable to whatever technology the business runs, including all legacy investments.
Once upon a time, companies bet big on web services. An enterprise that created thousands of SOAP services now has to transform them into REST services, and who knows what’s next. Because ignite is vendor-agnostic, you can generate RESTful APIs, SOAP services, and events, and support multiple developer frameworks with code templates. That means implementation is a technical choice you make when you develop your APIs, not a technical constraint you’re forced into.
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.