Notes API
Build a CRUD REST API for notes backed by a database.
Design, build and secure the servers, databases and APIs that power applications.
You have reached the end of the beginner stages. Prove what you learned with a project.
You have reached the end of the intermediate stages. Prove what you learned with a project.
You have reached the end of the advanced stages. Prove what you learned with a project.
Build a CRUD REST API for notes backed by a database.
Model books, members and loans, then write queries to answer questions about them.
Add registration, login with JWTs and role-based access to an API.
Reach meaningful test coverage with unit and integration tests.
Build a shortener with a cache in front of the database.
Send emails and process uploads through a message queue with retries.
Dockerise a service and deploy it with an automated pipeline.
Add rate limiting, pagination and monitoring to an API you expose publicly.
The same roadmap as a reading list: every stage, what each topic covers, and which ones are optional.
Clients, servers, DNS, HTTP and what happens between a click and a response.
Move around servers confidently: files, processes, permissions and shell basics.
Version control and collaboration through branches and pull requests.
Arrays, maps, trees, sorting and complexity: the vocabulary of efficient code.
JavaScript on the server, with a huge package ecosystem and shared skills with the frontend.
Readable and versatile, strong for APIs, automation and data work.
Fast, simple and built for concurrent network services.
Mature, statically typed ecosystems common in large enterprises.
Tables, keys, joins, indexes and transactions. The core of most backends.
A powerful open-source relational database to learn properly.
Map tables to code and evolve schemas safely with tools like Prisma.
When flexible JSON documents fit better than tables, for example MongoDB.
Keep hot data in memory to cut latency and database load.
Resources, verbs, status codes, pagination and versioning done consistently.
Sessions, JWTs and OAuth, and the difference between who you are and what you may do.
Never trust input; return clear, consistent errors.
Express, NestJS, FastAPI, Gin, Spring: choose the one for your language.
Let clients ask for exactly the data they need.
Describe your API with OpenAPI so others can use it.
Unit, integration and API tests that run on every change.
The most common web vulnerabilities and how to prevent them.
Protect endpoints from floods, scraping and credential stuffing.
Structured logs and metrics so you can see what production is doing.
Where to cache, how long, and how to invalidate without serving stale data.
Move slow or unreliable work off the request path with RabbitMQ or Kafka.
Understand the trade-offs before splitting a system apart.
Reason about load balancing, replication, sharding and failure.
Package an app and its dependencies so it runs the same everywhere.
Build, test and deploy automatically.
Compute, storage, networking and managed databases on a major cloud.
Backend developers build the server-side logic, databases and APIs that frontends and apps rely on, and keep them secure, reliable and fast.
Any of Node.js, Python, Go, Java or C# can lead to a good career. Choose one, learn it deeply, and the concepts transfer to the others.
You don't need to be an expert, but understanding how clients call your API makes you a much better backend developer.
Start with SQL. Relational concepts are widely applicable, and many NoSQL ideas are easier to understand afterwards.
© 2026 KamerLink. All rights reserved.