Skip to content

RESTful Terminology

Sharina Stubbs edited this page Jan 2, 2020 · 7 revisions

Function Name

  1. getBlogPost()
  2. addBlogPost()
  3. updateBlogPost()
  4. deleteBlogPost()

English

  1. get one blog post
  2. add blog post
  3. update blog post
  4. delete blog post

HTTP

  1. GET
  2. POST
  3. PUT
  4. DELETE

PATH

  1. /get-one
  2. /blog-post
  3. /blog-post
  4. /blog-post

CRUD

  1. read
  2. create
  3. update
  4. delete

CRUD

Create, Read, Update, Delete

Three ways to pass data with HTTP

  • Query parameter
  • request body - form will put data into the request body, or you can use jquery, or superagent on the frontend
  • add it to the path - path variable

Lives in the URL:

  • path variable
  • Query parameter

Projects of Note

  • Songr
  • Codefellowship
  • Spring apps

REST and RESTful and APIs in Java-401

From Michelle Ferreirae:

"REST is a cool vocab word that different people use to mean different things. Officially, it means a bunch of buzzwords about not saving state between requests. Realistically? REST means your URLs are structured like /restaurants/{id}/reviews , and you're using GET/POST/PUT/DELETE methods appropriately.

During Android, we mostly used GraphQL, which is decidedly NOT REST.

Your website can be RESTful, or your API can be RESTful, if it has URLs with that basic sort of structure. We never explicitly covered how to create a JSON API, but we saw an example with the provided TaskMaster backend Spring app; it's honestly really boring compared to Thymeleaf."

Resources

Clone this wiki locally