Backend is not scary — it is just logic with endpoints

Forget the cryptic acronyms and shadowy server rooms; backend development is less about arcane magic and more about elegantly connecting the dots.

For years, I (as a freelancer building websites) heard the whispers, the fear surrounding backend development. It was painted as a complex beast, requiring a deep understanding of databases, server configurations, and languages most mere mortals couldn't fathom. But when I actually dived in, I realized the "scary" part was mostly a self-imposed mental block. At its core, backend is simply logic – the instructions that tell your application what to do when a user interacts with it.

Think of your favorite app. When you click "save," something happens on a server. That "something" is backend code. It receives your request, processes it, and sends back a response. It’s a conversation between your browser (the frontend) and a remote computer (the backend). This conversation happens through something called endpoints – specific URLs that trigger particular actions. For example, /api/users might be an endpoint to fetch a list of users, while /api/users/create could be for adding a new one.

Let's get a little hands-on. Imagine we're building a simple to-do list app. On the backend, using Node.js and Express (a popular framework), we might define an endpoint to get all our tasks:

// server.js

const express = require('express');
const app = express();
const port = 3000;

let tasks = [
  { id: 1, description: 'Buy groceries', completed: false },
  { id: 2, description: 'Walk the dog', completed: true }
];

app.get('/api/tasks', (req, res) => {
  res.json(tasks); // Sends the tasks array as JSON
});

app.listen(port, () => {
  console.log(`Server listening at http://localhost:${port}`);
});

See? app.get('/api/tasks', ...) defines an endpoint. When a request hits /api/tasks, the code inside the function runs, sending back our tasks array. It’s this structured way of handling requests and sending responses that forms the backbone (pun intended) of backend development.

The "logic" part comes in when we want to do more. Maybe we want to add a new task. We'd create another endpoint, perhaps a POST request to /api/tasks, that receives data from the frontend and adds it to our tasks array.

app.use(express.json()); // Middleware to parse JSON bodies

app.post('/api/tasks', (req, res) => {
  const newTask = {
    id: tasks.length + 1,
    description: req.body.description,
    completed: false
  };
  tasks.push(newTask);
  res.status(201).json(newTask); // 201 Created
});

The key takeaway? Backend development isn't about knowing every single framework or database under the sun. It's about understanding how to structure your application's logic, how to handle incoming requests, and how to send back appropriate responses. It’s problem-solving, plain and simple.

As a freelancer, I find this fundamental understanding incredibly empowering. It allows me to build robust, dynamic websites and applications without getting bogged down by perceived complexity. If you're looking for someone to bring your web ideas to life, check out my services at https://hire-sam.vercel.app/.

So, next time you hear someone talk about the backend with trepidation, remind them: it’s just logic, with endpoints.