Back-End Development
Learn to build the APIs, databases, and server-side logic that power web applications. A technical track for people who want to work on the part of the product users don't see, but always depend on.
About this track
Back-end work is where APIs, databases, auth, and performance meet. You design and build REST services in Node with a small framework such as Express, store data in PostgreSQL or SQLite, peek at MongoDB for documents, prove behaviour in Postman, collaborate in Git, and deploy to a cloud host. The output is a service a frontend or mobile app can actually call. You should already be comfortable with at least one language at a basic level; this is not the place to learn what a variable is for the first time.
Who this track is for
People who already work with HTML, CSS, and JavaScript and want to understand what happens on the server.
Graduates who want to specialize in backend systems with practical, employer-relevant project work.
Learners who have completed a coding introduction and want to apply their knowledge in a backend context.
What you will learn
APIs, databases, security, and deployment, taught the way it tends to run in real teams: small changes, clear review, and code you can trace from your machine to production.
Server-side fundamentals and Node.js
- How the web works from the server's perspective: requests, responses, and where your API sits
- Node.js: runtime, modules, and the event model
- Building a basic HTTP server and understanding layers before frameworks
- Introduction to Express or a similar framework, routing, middleware, and separation of concerns
Team workflow: Git, remotes, and code review
- Local Git: branch, commit, push, pull, history teammates can follow
- GitHub or GitLab: remotes, PRs/MRs, and sensible branch habits
- Code review: clear diffs, useful feedback, small reviewable changes
- Issues and tasks: link work to tickets, know “done” before you ask for review
- Same discipline for backend: reviewable API changes, careful migrations, Postman to back your PR
REST APIs, resources, and structured backend thinking
- REST as a way to model resources and operations, not only memorising methods and status codes
- Designing consistent URL patterns, payloads, and error shapes other teams can rely on
- Validation, authorisation boundaries, and logging enough context to debug production issues
- Verifying behaviour in Postman: collections, environments, and regression checks before you merge
Databases, persistence, and architecture basics
- Relational modelling with PostgreSQL or SQLite: tables, keys, and relationships your API will query
- Writing and tuning the queries you need: SELECT, INSERT, UPDATE, DELETE, and when transactions matter
- Connecting persistence to application structure so data access does not sprawl across the codebase
- MongoDB introduction: when document storage fits, and how it changes how you think about schemas
- Lightweight architecture habits: config, boundaries between layers, and what “maintainable” looks like in a small service
Auth, security, deployment, and delivery discipline
- Authentication: sessions, tokens, and JWTs, and trade-offs teams actually argue about
- Authorisation and protecting routes; common security pitfalls and how to avoid them
- Deploying Node APIs to a cloud platform (e.g. Render, Railway, or Fly.io): environments, secrets, and HTTPS
- Keeping deploys predictable: what merges to main, what gets tagged, and how review ties to release
Tools & technologies
What we use in the project, short list; how you work with it lives in the curriculum above.
Node.js
Runs JavaScript on the server. Powers APIs, scripts, and most web tooling today.
Express
Minimal Node.js web server framework. Routes, middleware, and JSON APIs in a few lines.
PostgreSQL
Relational SQL database. Strong types, transactions, JSON support — the safe default.
MySQL
Used as part of this track's hands-on toolkit.
SQLite
Used as part of this track's hands-on toolkit.
MongoDB
Document database that stores JSON-like records. Flexible schemas for fast iteration.
Postman
API request builder. Hit endpoints, inspect responses, share collections with the team.
Git
Distributed version control. Track changes, branch, merge, and roll back code history.
GitHub
Hosted Git plus pull requests, issues, code review, and CI — where teams ship code together.
GitLab
Used as part of this track's hands-on toolkit.
Render
Used as part of this track's hands-on toolkit.
Railway
Used as part of this track's hands-on toolkit.
Fly.io
Used as part of this track's hands-on toolkit.
Java
Referenced as common stacks; the hands-on project stays Node.js-based.
Kotlin backends
Referenced as common stacks; the hands-on project stays Node.js-based.
Cloud host may vary by intake. Free tiers where possible.
How the learning works
Not self-paced video content. A structured programme with real outputs and structured feedback.
Build a real API
You construct a working REST API throughout the track, adding routes, connecting a database, and securing it as you progress.
Understanding over copying
Mentor sessions focus on why the code works, not just what to type. Debugging is part of the learning.
Deployment included
The track ends with your API deployed and accessible, not just running on localhost.
What this prepares you for
Realistic, honest expectations. The track gives you foundation and practice. What you do with it determines what comes next.
A deployed REST API with database integration
Understanding of how backend systems are structured, tested in Postman, and secured
Ability to design and document API endpoints with Git-backed collaboration
Foundation for junior backend developer, API developer, or full-stack developer roles
Back-End Development: common questions
Track-specific answers: prior knowledge needed, what you build, tools used, and how to get started.
Still have a question not covered here?
Start a conversationReady to start the Back-End Development track?
Contact us to confirm the next intake date and ask any questions before you commit.
Contact Folowise if you have questions before applying.