This is the stage of the life cycle where requirements are translated into something tangible that can be built and delivered. It requires an understanding of all functional and non-functional requirements. A domain model and a conceptual design are produced based on a series of well-thought-out design decisions.
The concept design should, among other things, answer questions: what is the business domain of an API and its bounded context? What business capability does the API offer? What API architectural style is to be adopted (for example, GraphQL for public interface, or gRPC for inter-service communication)? What does the end-to-end solution look like, including the patterns (for example, API aggregator and CQRS) and technical ...
