REST Service

The rest package provides convenience functions to define a serverless REST style service.

The package uses three concepts:

  • Routes: URL paths that resolve to a single go struct
  • Resources: go structs that optionally define HTTP method (GET, POST, etc.).
  • ResourceDefinition: an interface that go structs must implement in order to support resource-based registration.


Routes are similar many HTTP-routing libraries. They support path parameters.


Resources are the targets of Routes. There is a one to one mapping of URL Routes to go structs. These struct types must define one or more member functions that comply with the valid function signatures for AWS Lambda.

For example:

import (
  spartaAPIGateway ""
// TodoItemResource is the /todo/{id} resource
type TodoItemResource struct {

func (svc *TodoItemResource) Get(ctx context.Context,
  apigRequest TodoRequest) (interface{}, error) {
  // ...
  return spartaAPIGateway.NewResponse(http.StatusOK, "All good!"), nil

As the resource will be exposed over API-Gateway, the return type must be a struct type created by spartaAPIGateway.NewResponse so that the API-Gateway integration mappings can properly transform the response.

Resource Definition

The last component is to bind the Routes and Resources together by implementing the ResourceDefinition interface. This interface defines a single function that supplies the binding information.

For instance, the TodoItemResource type might define a REST resource like:

// ResourceDefinition returns the Sparta REST definition for the Todo item
func (svc *TodoItemResource) ResourceDefinition() (spartaREST.ResourceDefinition, error) {

  return spartaREST.ResourceDefinition{
    URL: "/todo/{id}",
    MethodHandlers: spartaREST.MethodHandlerMap{
      // GET
      http.MethodGet: spartaREST.NewMethodHandler(svc.Get, http.StatusOK).
          MemorySize: 128,
          Timeout:    10,
  }, nil

The ResourceDefinition function returns a struct that defines the:

  • Route (URL)
  • MethodHandlers (GET, POST, etc.)

and for each MethodHandler, the:

  • HTTP verb to struct function mapping
  • Optional LambdaFunctionOptions
  • Expected HTTP status codes (StatusCodes)
    • Limiting the number of allowed status codes reduces API Gateway creation time
  • Additional IAM Privileges needed for this method


With the REST resource providing its API-Gateway binding information, the final step is to supply the ResourceDefinition implementing instance to RegisterResource and return the set of extracted *LambdaAWSInfo structs:

  todoItemResource := &todoResources.TodoItemResource{}
  registeredFuncs, registeredFuncsErr := spartaREST.RegisterResource(api, todoItemResource)

See the SpartaTodoBackend for a complete example that implements the TodoBackend API in a completely serverless way!