Home / Questions / 184036
Accepted
Virgilio La Rosa
Asked: 2020-07-26 16:15:47 +0800 CST 2020-07-26 16:15:47 +0800 CST

Optimize the response of a service in an Api-Rest with Spring Boot

  • 772

Good morning, I am currently developing a rest api with Spring Boot :: (v1.5.9.RELEASE) to control the management of a table called File, which persists with other entities,

File Table

The controller to call the service is as follows: @RestController public class ExpedientController { @Autowired protected ExpedientService expedientService; @Autowired protected ExpedientSubserviceService expedientSubserviceService; protected UserService userService; protected ObjectMapper mapper;

@CrossOrigin(origins = "*")
@RequestMapping(value = "/api/expedient/saveOrUpdate",method = RequestMethod.POST)
public RestResponse saveOrUpdate(@RequestBody String expedientJSON) throws JsonParseException, JsonMappingException, IOException {
    this.mapper= new ObjectMapper();
    Expedient expedient=this.mapper.readValue(expedientJSON,Expedient.class);
    this.expedientService.save(expedient);
    String message = Integer.toString(expedient.getId())+" "+Integer.toString(expedient.assured.getId());
    return new RestResponse(HttpStatus.OK.value(), message);

}
@CrossOrigin(origins = "*")
@RequestMapping(value = "/api/expedient/getAll", method = RequestMethod.GET)
public List<Expedient> getAll() {
    return this.expedientService.findAllByDeletedAt(0);
}

@RequestMapping(value = "/api/expedient/delete", method = RequestMethod.POST)
public void deleteExpedient(@RequestBody String expedientJson) throws Exception {
    this.mapper = new ObjectMapper();

    Expedient expedient = this.mapper.readValue(expedientJson, Expedient.class);

    if (expedient.getId()==0) {
        throw new Exception("El id esta nulo");
    }
    this.expedientService.delete(expedient.getId());
}

The Json of the query is large due to the number of objects that persist between them. Is it recommended that separate queries be made without the need to bring all the information of the persisted entities in the json? Or is there some compression method that can be used.

java

1 Answers

  1. Best Answer

    Hello, it depends a lot on the architecture of the service and how it would be consumed, but you can do several things:

    1. Design a DTO's scheme to show less data of your entities, that is, Ids and only essential information.
    2. Enable Gzip compression in your application link
    3. If this data is going to be consumed within a grid or displayed on a website, you can enable pagination by extending the PagingAndSortingRepository interface in your repositories and with this you will bring the paginated records, greatly relieving the query.

    Example Pagination:

    public interface ExpedientRepository extends  PagingAndSortingRepository<Expedient ,Long> {
}

    I hope it has been helpful for you

    Greetings.

    • 0