The BFF pattern accelerates innovation because the team that implements the frontend also owns and implements the backend service that supports the frontend. This enables teams to be self-sufficient and unencumbered by competing demands for a shared backend service. In this recipe, we will create a CRUD BFF service that supports data at the beginning of its life cycle. The single responsibility of this service is authoring data for a specific bounded context. It leverages database-first Event Sourcing to publish domain events to downstream services. The service exposes a GraphQL-based API.
Implementing a GraphQL CRUD BFF
Getting ready
Before starting this recipe, you will need an AWS Kinesis Stream, such as the one created...