spring-projects / spring-projects/spring-data-rest

Reducing amounts of hits

Open
#82 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: waiting-for-triage
Dominant language
Java
Stars
958
Forks
568
PR merge metrics
No merged PRs in 30d

Description

Hello,

This is more a question than a feature request or a bug but I thought it still can be the place to ask it (sorry if it's not).

I'm here as a standard Web developer making web sites with a Spring JSON API for backend. I discovered the Spring Data Rest project with great expectations because the most parts of all my servers code are always about publishing some CRUD api.

But since I test Spring Data Rest, I'm facing a problem: the number of server hits. I perfectly understand concepts of HATEOAS, urls, links and the concept of navigation in a REST API and I also appreciate it.

The problem I'm facing is that for some pages which present lots of data, I have to follow lots of links to get all I need and it can lead to hundreds of requests and it's just not possible. I searched but didn't find a way to resolve this question by configuration or anything else and it's currently blocking me to use Spring Data Rest in my projects. (perhaps something around cursom serializer, but I can't override everything)

Finally my question(s): am I missing something? is Spring Data Rest not designed for what I want to do with it?
And if I'm not missing something, can't you add some request parameter wich tell exporter to directly resolve some links?

I hope my question has not already be answered but if so, I didn't find it. I also hope my english is good enough to be understandable ;)

Thanks in advance.
Matthieu

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing Spring Data REST's current exporter behavior for resolving links and the existing request-parameter and serialization entry points; no specific files or tests are named in the issue. The scope is complete only once the desired link-resolution behavior, configuration or parameter design, and acceptance tests are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.