# Bender

Bender quotes as a web service

Bender is a small API which allows you to run a BaaS stack (Bender as a Service) for those times you really wish you could tell a web app to bite your shiny metal ass.

TIP

You can go directly to Benderopen in new window and get your dose of Futurama if you're more interested in that than the API docs.

# Background

It is primarily designed to be a simple, straightforward to implement, API service with limited external dependencies to be used as a technology evaluation platform for micro-service technologies. Over the course of its existence, it has provided me with a means to evaluate some of the following practices and technologies (and many others I'm sure I've forgotten).

  • ASP.NET Core
  • Serving multiple content types based on Accept headers
  • CI/CD to Google Kubernetes Service with Helm and Azure DevOps
  • Google AppEngine
  • Google Firebase
  • Golang + girderopen in new window
  • Azure CosmosDB
  • Azure Table Storage
  • CI/CD to Azure Kubernetes Service with GitHub Actions
  • Rust + Rocket
  • Rust + actix-web
  • Azure Blob Storage in Rust

# Running your own

We publish a Docker image for Bender on the DockerHub. The fastest way to get Bender running on your own laptop or cluster is to do the following.

docker run --rm -it -p 8000:8000 sierrasoftworks/bender:latest
1

If you're using Kubernetes, you can also deploy Bender and a Service representing it by running the following. Doing so will expose a http://bender-server service within your cluster.

kubectl apply --namespace bender -f https://raw.githubusercontent.com/SierraSoftworks/bender/main/.deploy/deployment.yml
kubectl apply --namespace bender -f https://raw.githubusercontent.com/SierraSoftworks/bender/main/.deploy/service.yml
1
2

# API

# Quotes

# GET /api/v1/quote/{who?}

This endpoint allows you to fetch a random Futurama quote. The quote will be returned in the best content type we can negotiate based on your provided Accept header, defaulting to JSON if you do not provide an Accept header (I see you, lazy API client developers).

GET /api/v1/quote HTTP/1.1
Host: bender.sierrasoftworks.com
Accept: application/json
1
2
3

The following content types are supported:

  • application/json
  • text/html
  • text/plain

If you provide a {who} component (which is optional) you can specify which Futurama character's quotes you'd like to receive.

GET /api/v1/quote/bender HTTP/1.1
Host: bender.sierrasoftworks.com
Accept: application/json
1
2
3
# 200 OK

Usually, you'll be greeted with a 200 OK response from this endpoint (unless we've misconfigured things and don't have any quotes available for you, or you've specified a {who} which we don't have quotes for). Depending on the Accept header you have provided, you may receive one of the following responses.

# application/json
{ "who": "Bender", "quote": "Bite my shiny metal ass." }
1
# text/plain
Bite my shiny metal ass. – Bender
1
# text/html
<html>
    <head>
        <style>
            body {
                font-family: Sans-serif;
            }

            figure {
                margin: 20px;
            }

            blockquote {
                margin-left: 1em;
            }

            figcaption {
                margin-left: 2em;
                font-size: 0.8em;
                font-weight: bold;
            }

            figcaption::before {
                display: inline;
                content: "–";
                padding-right: 0.5em;
            }
        </style>
    </head>
    <body>
        <figure>
            <blockquote>Bite my shiny metal ass.</blockquote>
            <figcaption>Bender</figcaption>
        </figure>
    </body>
</html>
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
# 404 Not Found

If you specify a {who} which we don't have quotes for, then we'll respond with a 404 Not Found status code. In this case, the response will always be application/json encoded, regardless of your Accept headers.

{
    "code": 404,
    "error": "Not Found",
    "message": "There are no quotes available right now, please add one and try again."
}
1
2
3
4
5
# 500 Internal Server Error

If things really do go sideways for us, then you might find a coveted 500 Internal Server Error. Bender, for the most part, is pretty simple so this should (hopefully) be rare, but it's also more of a research project than a full-blown production service, so not that rare. In any case, these get reported to us automatically and we'll set our interns to fixing the issue ASAP.

{
    "code": 500,
    "error": "Internal Server Error",
    "message": "We ran into a problem, this has been reported and will be looked at."
}
1
2
3
4
5

# Health and Telemetry

# GET /api/v1/health

This endpoint is designed to provide a low-cost query surface for automated health probes and lifecycle checks. If you're familiar with Kubernetes livenessProbes, this is the endpoint you would point those at for Bender.

GET /api/v1/health HTTP/1.1
Host: bender.sierrasoftworks.com
1
2
# 200 OK

This endpoint should always return a 200 OK status code, unless the service is down, in which case the frontend proxy may return a response to the caller (if present).

{ "ok": true }
1