Welcome to this summary of the full Abstracted API and Service Lifecycle Design stage. You can download the full whitepaper at the end of this article.
The lifecycle is broken down into 3 stages, and we will be releasing a whitepaper for each one. The 3 stages are:
Key definitions and reasoning behind this series
The digitalML version of the lifecycle takes a design-first approach, and focuses on plan, design and build with integration into the run phase (and because the plan, design and build stages are working with an abstraction layer, this is suitable for any runtime environment). We do this because we believe this enables you to become an intelligent enterprise and gain competitive advantage.
Overview – what happens in the design stage and why it is so important?
Taking a design-first rather than code-first approach is crucial for development at scale. It ensures everything that’s built is globally reusable, consistent and secure, and encourages proper governance and standards without compromising on speed. This is so valuable because it means even the largest incumbent enterprises can compete with the Amazons of the world and rapidly innovate to launch into new markets.
We are now seeing large enterprises using this design-first approach to deliver real results. For example, a leading Healthcare Insurance provider and ignite customer has leveraged their abstraction layer of digitized business functions to save 177 hours and $10k per API developed. This has led to an incredible total saving of $9.3m over a 3-year period. This is just the cost of building the API – there is an even more value in having abstracted design available for reuse as components. Sounds too good to be true? Well we’re here to tell you it’s a reality and help you achieve this success too!
On a practical level, during the design stage a more technical team take the design request from the plan stage and add or extend more IT capabilities that are either missing or not quite right. Where appropriate, components of existing digital building blocks can be reused to help flesh out the design. The appropriate runtime output template is also chosen.
Example use cases
*Note to reader: Throughout all the examples in this series we will be assuming that the
enterprise has built an abstraction layer of digitized business functions and are using a platform
like ignite to maintain and extend it.
Value of abstracted design
By using the approach we’ve discussed, your abstracted design, rather than the code itself, becomes the artifact of the greatest value. Here’s why:
- Your design and all the information contained in it is not tied down to any coding format or technology – this means you can easily adapt to changing environments and new technologies
- You can bake-in proper governance and standards – by making available a domain-based information model, all your designs will be consistent
- Everything is reusable – because the design is agnostic of any coding format, it can be used time and time again by multiple consumers – the endpoints are infinite
Download the full whitepaper
Download the full whitepaper now to:
- Understand the critical capabilities your enterprise needs for success in the design stage
- Benchmark where your enterprise is in maturity of this approach, and identify the next steps to competitive advantage
- Learn how the ignite platform supports the design stage