We're sorry but this app doesn't work properly without JavaScript enabled. Please enable it to continue.

This lesson's interactive features are locked, please to keep using them

You're on assignment part 2/2 for this lesson.

HTTP CRUD Database Lifecycle

We talked about how a "create" operation flows through a web application. Let's talk about a "read."

We'll use an example scenario from the CashPal app. Our product manager wants to show profile data on a user's settings page. Here's how we could engineer that feature request:

  1. First, the front-end webpage loads.
  2. The front-end sends an HTTP GET request to a /users endpoint on the back-end server.
  3. The server receives the request.
  4. The server uses a SELECT statement to retrieve the user's record from the users table in the database.
  5. The server converts the row of SQL data into a JSON object and sends it back to the front-end.