Breaking News: Grepper is joining You.com. Read the official announcement!

Exposing Reactive Restful APIs ( all the GET / POST / PUT / DELETE )

Pragya Keshap answered on February 15, 2023 Popularity 1/10 Helpfulness 1/10

answer Exposing Reactive Restful APIs ( all the GET / POST / PUT / DELETE )

Exposing Reactive Restful APIs ( all the GET / POST / PUT / DELETE )

Comment

Below are the advantages we will get with reactive APIs.

Asynchronous and Non-Blocking → Reactive programming gives the flexibility to write asynchronous and Non-Blocking applications.

Event/Message Driven→ The system will generate events or messages for any activity. For example, the data coming from the database is treated as a stream of events.

Support for backpressure → Gracefully we can handle the pressure from one system to on to the other system by applying back pressure to avoid denial of service.

Predictable application response time → As the threads are asynchronous and non-blocking, the application response time is predictable under the load.

Better utilization of system resources → As the threads are asynchronous and non-blocking, the threads will not be hogged for the I/O. With fewer threads, we could able to support more user requests.

Scale based on the load

Move away from thread per request → With the reactive APIs, we are moving away from thread per request model as the threads are asynchronous and non-blocking. Once the request is made, it creates an event with the server and the request thread will be released to handle other requests.

@RestController
15
public class ProductController {
16
17
    @Autowired
18
    private ProductService productService;
19
20
    /**
21
     * This endpoint allows to create a product.
22
     * @param product - to create
23
     * @return - the created product
24
     */
25
    @PostMapping("/product")
26
    @ResponseStatus(HttpStatus.CREATED)
27
    public Mono<Product> createProduct(@RequestBody Product product){
28
        return productService.save(product);
29
    }
30
31
    /**
32
     * This endpoint gives all the products
33
     * @return - the list of products available
34
     */
35
    @GetMapping("/products")
36
    public Flux<Product> getAllProducts(){
37
        return productService.getAllProducts();
38
    }
39
40
    /**
41
     * This endpoint allows to delete a product
42
     * @param id - to delete
43
     * @return
44
     */
45
    @DeleteMapping("/product/{id}")
46
    public Mono<Void> deleteProduct(@PathVariable int id){
47
        return productService.deleteProduct(id);
48
    }
49
50
    /**
51
     * This endpoint allows to update a product
52
     * @param product - to update
53
     * @return - the updated product
54
     */
55
    @PutMapping("product/{id}")
56
    public Mono<ResponseEntity<Product>> updateProduct(@RequestBody Product product){
57
        return productService.update(product);
58
    }
59
}

https://dzone.com/articles/build-reactive-rest-apis-with-spring-webflux

Popularity 1/10 Helpfulness 1/10 Language javascript

Source: Grepper

Tags: get javascript post put reactive

Link to this answer
Share Copy Link

Contributed on Feb 15 2023

Pragya Keshap

0 Answers Avg Quality 2/10

Exposing Reactive Restful APIs ( all the GET / POST / PUT / DELETE )

Contents

More Related Answers

Exposing Reactive Restful APIs ( all the GET / POST / PUT / DELETE )

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.