From the course: Spring Boot and React: Build Scalable and Dynamic Web Apps

Unlock the full course today

Join today to access over 24,700 courses taught by industry experts.

Challenge: REST

Challenge: REST

From the course: Spring Boot and React: Build Scalable and Dynamic Web Apps

Start my 1-month free trial Buy for my team

Challenge: REST

“

(upbeat music) - [Instructor] So now it's time for another challenge exercise. Once again, the instructions, I want you to implement the REST API pattern for the three other web models. So you're going to go ahead and create the RestController, you're going to wire in the service to each one of them, and of course, you need to test your output. Now I want you to think about something here. A product has a vendor, so how do you want to expose those two distinct entities? And there's definitely schools of thought on how to handle those. I personally, would leave them as very separate entities and allow your consumer to decide when to load the vendor or not. However, there can be an argument to state that you should embed the vendor into the product itself and return it because most likely that data is going to be needed. Now, again, I will leave that up to you as a decision to make. I've told you where I'm going to go…

Contents