Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    I think it would make more sense to ask how to design this API in a REST style. I am not a REST expert, but I think without this restriction, web API design is quite arbitrary. Commented Nov 28, 2024 at 7:00
  • 1
    A tournament_results table (tournament_id, player_id, player_name, placement...) If this table has the player id, why does it also need the player name? Commented Nov 29, 2024 at 22:18
  • 1
    You've run in to one of the common problems of REST API design - if a request returns a list of related entities, should you be 'pure' and just return the ID's and make the front end do N+ queries to get the related data? Or should you be less pure but only require a single request from the front end? This gets even more complicated as you add more use cases, and you need to worry if you're overquerying. I'd err on the side of 'be less pure and get the data you need in one request'. Alternatively you could use something like GraphQL to get the data you need on subentities. Commented Dec 3, 2024 at 3:18
  • @JohnGordon Due to the way the ranking system is set up (country specific), tournaments may include foreign players that are not "registered" and thus do not have an ID, but the results page still needs a name to display, so it gets it from there Commented Dec 3, 2024 at 22:23