Web Theory 2

Intro

Goals

  • Dive deeper into how the web works on the back end

  • Learn back-end web concepts

How the Web Works

The Big Question

“What happens when I visit https://google.com?”

How the Web Works

_images/response.jpg

Let’s dive deeper into what happens on the back-end part of the request/response pattern.

Server receives request

_images/catch.jpg _images/pre-routing.png

Request is routed to controller

_images/routing.png

Back-end logic

_images/back-end-logic.png

Response is generated

_images/response-gen.png

Back End Concepts

MVC

Model View Controller

  • A back-end web design pattern

  • Model: database tables and object-oriented code to represent them

  • View: HTML templates or Javascript code used to generate responses in HTML

  • Controller: a section of the back-end code that handles certain URLs

_images/mvc.png

Monolith

  • A monolith is a term for a traditional web application in which all logic is housed in one app

  • There is a single code base that holds back-end logic for the entire application

Microservices

  • An alternative to the monolith

  • Several sepearate, smaller web applications exist to handle the various requests

  • Helps with scalability, maintainability, and more

  • Complexity also increases

Other Web Frameworks

If you’re passionate to learn about back-end web development, here is a list of other popular frameworks to check out:

  • Python: Flask, Django

  • Java: Spring Boot

  • Javascript: Next.js, Meteor

  • PHP: Laravel

  • Ruby: Rails

The End