Frontend vs Backend — What's Actually Different?

This is the first question you hit when starting to learn coding. "Frontend developer," "backend developer," "fullstack" — these words flood job postings and YouTube tutorials, but it's hard to grasp what's actually different.

Use a lab analogy and it clicks instantly.

The Lab Has a Front and Back Too

Frontend = Lab Bench

The visible workspace. Pipettes, reagent bottles, gel images — everything the researcher touches and sees directly. On the web, everything you see in the browser is the frontend. Buttons, text, images, input forms, graphs — everything the user sees and clicks.

Backend = Instrument Room + Database

Behind the bench: the sequencer, qPCR machine, LIMS server. The researcher submits a sample, the instrument analyzes it, and stores the results in a database. On the web, the server plays this role. When a user clicks "Search," the server finds results in the database and sends them back.

Fullstack = A researcher who does both bench work and instrument operation. If you've done everything yourself in a small lab, you're already a fullstack researcher.

Frontend vs Backend Through NCBI

Think about searching for a gene on NCBI:

1. Type "TP53" in the search box and click Search → Frontend handles this
2. The request is sent to NCBI's server → Network (the fetch you learned earlier)
3. The server finds TP53 information in the database → Backend handles this
4. It packages the results as JSON and sends them back → Backend handles this
5. The received data is displayed nicely on screen → Frontend handles this

Web services run through the collaboration of these two parts. Neither side alone makes a complete product.

Framework vs Library

While studying coding, you'll encounter debates like "Is React a framework or a library?" This can be explained with lab analogies too.

Library = Individual Reagent

The researcher takes it out when needed. Pulling Taq polymerase from the reagent cabinet and adding it to your protocol. You lead the experiment flow, and the reagent is a tool you call.

My code → calls the library
(I'm in control)

Framework = Experiment Kit

When you buy a kit, the protocol is predetermined. "Add solution 1 → 65°C for 5 minutes → add solution 2" — the kit drives the experiment flow, and the researcher just swaps out samples within that structure.

Framework → calls my code
(Framework is in control)

Using a kit means you don't need to design the experiment from scratch — just follow the validated protocol. Frameworks are the same — they handle repetitive work like login, routing, and error handling, letting you focus on core features.

Which Side Fits Bio Researchers?

Honest answer: backend (data processing) is the closer fit.

Your main work is data analysis. Genome sequence processing, experiment result statistics, pipeline automation — these are all backend territory. Working with data in Python is itself backend work.

Frontend (HTML, CSS, React) is a tool for showing results. When you want to share analysis results with colleagues, when you want to build a dashboard — that's when you need the frontend.

You don't need to aim for fullstack from the start. Begin with data handling in Python, and layer on frontend skills as needed.

Web Tech Is a Tool, Not the Goal

Summarizing the difference between general web developers and bio researchers:

You're not trying to become a "web developer." You're a researcher who works with data, and the web is a window to show your results to the world. That's also why DevBench's A-2 track (web development) exists — to give you the power to deploy analysis results on the web.