API Lifecycle: Build Stage (Part 3 of 4)

  • Plan — Ideate, Plan Product, or See Progress
  • Design — Create New or Extend Existing API
  • Build — Generate Artifacts
  • Run — Deploy Artifacts Using ignite or Runtime Manager

What does Generate Artifacts mean…

Building fast means catching the big wave… and staying there

Consistency, Reuse, & Alignment

Eliminating Human Error


Deep-Dive View of Generated Artifacts

  • Swagger Specification — for a standard, language-agnostic interface to REST APIs
  • OpenAPI — for a publically available API
  • WSDL — XML format that describes your web service (SOAP)
  • Custom message specification — for event specifications
  • Generations — for C# (yes, even for C#!)

So now the question is…

  • Business Logic — See: Plan stage.
  • Implementation — Start work on the Service Contract.
  • User Experience — Connecting to the front-end.
  • Backend Connections — See: Design stage.
  • Go Bowling —



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store



Large enterprises use our ignite Platform for digital recombination, APIs & Services at scale, Rapid IT Modernization, and Business & IT alignment