API Resume

A résumé is usually a PDF. As a small experiment, inspired by Eric Lake’s API résumé, I wanted mine to be something a developer could query.

Solo, in October 2023: a small Express app, with most of the interesting work in the middleware that decides who gets an answer.

• Endpoints for experience, projects, education and contact, a combined /api/resume, and a menu at /api.
• Only answers Postman (other clients get a 403), rate-limits each IP per day (429), and meets any non-GET request with a joke 500.
• Express and Mongoose on MongoDB, deployed to Vercel with Vercel Analytics.

1. Middleware as the personality

   The client check, the per-IP daily limit and the joke for non-GET requests all run ahead of the routes, so each section’s route stays a plain read.

2. Classic layers

   Routes, controllers and Mongoose models per résumé section, one file each.

1. 01PostmanThe only client allowed
2. 02MiddlewareClient check, daily limit, easter egg
3. 03Routesexperience, projects, education…
4. 04ControllersOne per section
5. 05MongoDBMongoose models

One Express app; each request passes the middleware before reaching a section’s route.

Node.js

Express

MongoDB

Mongoose

Vercel

• GitHub

The project’s links and the public sources this write-up draws on.