Every blog, store, and app runs on four operations: Create, Read, Update, Delete. They map to HTTP verbs and SQL statements. Press an operation and watch a post travel from the client, through the server, into the database tower — the exact round trip a full-stack blog performs.
POST /api/posts → server validates the body, then INSERT INTO posts (...) VALUES (...). The DB assigns an auto-increment id and returns the new row. This is how "Publish" works.GET /api/posts → SELECT * FROM posts. No body, safe & idempotent — you can repeat it endlessly with no side effects. The homepage feed is one big Read.PUT /api/posts/:id → UPDATE posts SET title=? WHERE id=?. Editing a draft. PATCH updates part of a row; PUT replaces it. Always scope with a WHERE clause or you rewrite the whole table.DELETE /api/posts/:id → DELETE FROM posts WHERE id=?. Removing a post. Many apps prefer a soft delete (a deleted_at flag) so content is recoverable and analytics stay intact.