Issuing an API request

The transaction starts right from when an API request comes into our system and routes to a controller or a resolver.

The transaction starts right from when an API request comes into our system and routes to a controller or a resolver.

# Using CURL to send an HTTP POST to a RESTful API

curl -d \
 '{"email":"khalil@apollographql.com", "password":"changeit"}' \
 -H "Content-Type: application/json" \
 -X POST https://api.dddforum.com/v1/users/new

If we're into GraphQL, it might look more like this.

# Using a GraphQL mutation to issue issue a command 
# into our system.

mutation {
  createUser(email: "khalil@apollographql.com", password: "changeit") {
    accessToken
    refreshToken
  }
}

Nonetheless, because we're using a Hexagonal Architecture, the type of API that we use doesn't affect how our command works. It just affects what calls our command. Let's not forget that GraphQL and RESTful APIs, while we can spend a lot of time on their design, are simply API styles that belong to the Infrastructure Layer and should have zero say as to how…