Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript REST APIs with Express Getting to Know REST APIs HTTP Methods and CRUD Operations

Posted by Sarah Krabacher
.a{fill-rule:evenodd;}techdegree seal-36
Sarah Krabacher
Full Stack JavaScript Techdegree Graduate 16,097 Points

Is Create a rough equivalent to Get or to Post?

at 0:37 the video implies the Create and Get are rough equivalents... wouldn't Create and Post be the actual rough equivalent? Create = Post, Read = Get, Update = Put, Delete = Delete.

Blake Larson
Blake Larson
13,014 Points

Correct. POST routes are often where some sort of data model is created. GET requests are for a return of some sort of data.

2 Answers

James Crosslin
.a{fill-rule:evenodd;}techdegree seal-36
James Crosslin
Full Stack JavaScript Techdegree Graduate 16,882 Points

I believe that order was used because it is the conventional order we see HTTP methods listed in documentation. At 1:27 in the video, Treasure specifically states and has on her slides that GET correlates to 'Read' and POST correlates to 'Create'.

Ed Pham
Ed Pham
3,102 Points
Ed Pham
Ed Pham
3,102 Points

In most scenarios, I believe it is more appropriate to POST data to CREATE a new entity rather than making a GET request. However, theoretically, it is possible to implement CREATE with either a GET or POST request.