A REST endpoint is a network-accessible operation a client can call over HTTP. In Spring, it is a controller action mapped to an HTTP method and path. section 10.1
Spring MVC handles the request, but the response differs from a page-rendering flow: the controller’s return value goes directly into the HTTP response body instead of being used to find a view. Mark a method with @ResponseBody, or use @RestController on the class to apply that behavior to its actions. section 10.1 section 10.2
A small endpoint
A HelloController action mapped with @GetMapping("/hello") can return "Hello!" as the response body. Call it with `curl http://localhost:8080/hello`; the example returns `Hello!`. section 10.2
Figure 10.2 When implementing REST endpoints, the Spring MVC flow changes. The app no longer needs a view resolver because the client needs the data returned by the controller’s action directly. Once the controller’s action is completed, the dispatcher servlet returns the HTTP response without rendering any view.

Follow how Spring MVC returns the controller’s data directly to the client without rendering a view. section 10.1
Endpoints connect web or mobile clients to a backend, and can also let backend services communicate. Consider practical limits: slow actions, large requests, or too many concurrent calls can disrupt communication or overload an application. section 10.1






























