How the whole app fits together
A full stack app has a front end, a back end and a database. Follow one click from the page through fetch, the Go server and the database and back, with every term from the earlier lessons.
Try it
- Request journey – Follow one click from the page through fetch, the internet, the Go server and the database, and back, step by step.
Transcript
A full stack app has three layers. The front end is what the visitor sees: H T M L, C S S and JavaScript in the browser. The back end is the Go server. And the database keeps the data. Like a restaurant: the dining room, the kitchen and the pantry.
Follow one click. The visitor presses Add. JavaScript calls fetch, which sends a request. The server receives it, checks it, asks the database to save it, and sends back a response.
Back in the page, JavaScript reads the response and changes the D O M to show the new task. Every term from the earlier lessons has a place in this journey.
Each layer has one job. The front end shows things and collects input. The back end decides and checks. The database remembers. Keeping the jobs apart makes an app easier to understand and to fix.
Remember: front end, back end and database. One click travels through all three and back, and each layer has one job.
More in this series
1:2549Planning a project
Plan before you code: user stories, wireframes on paper, a list of tables and endpoints, and small steps with a done-when for each.
1:1750Staying safe as a developer
Habits that keep you and others safe when you build apps: no secrets in code or Git, made-up test data, never trusting input, crediting other people's work and being kind.
1:2351Deploying an app
From localhost to the home network to the internet: what a server computer, a domain name, DNS and HTTPS do, and why public means more risk.
1:2052What to learn next
A map of next steps after the first year: front-end frameworks and TypeScript, more Go and databases, algorithms, games, security and open source, and how to keep learning safely.