Students API – a Server with a Database on kodkod | Intro Course

Connecting Routes to Database Actions: the Architecture

Mon, 01 Jan 0001 00:00:00 +0000

What will we learn?

Now we connect everything: the server from the backend and FastAPI topic, and the database from the databases topic. This lesson focuses on the architecture, that is, how the parts connect, and implements the first two Endpoints (reading). In the next lesson, the rest.

Students API — Full CRUD: POST, GET, PUT and DELETE on the Database

Mon, 01 Jan 0001 00:00:00 +0000

What will we learn?

We complete the API according to the mapping table:

POST /students → INSERT → 201.
PUT /students/{id} → UPDATE → 200 / 404 / 409.
DELETE /students/{id} → DELETE → 204 / 404.
An input model (Pydantic) and shared business validation (400).

Why do we need this?

This is the short project that sums up Server + Database + CRUD, as the syllabus defines. At the end of the lesson there is a real API: an app, a Frontend or another service can create, read, update and delete students, and the data is saved in the database.

Testing the System: Swagger UI, curl and a Test Script in Python

Mon, 01 Jan 0001 00:00:00 +0000

What will we learn?

A server that was not tested is a server you cannot be sure works. We will learn three ways, from the manual to the automatic: