REST is still going strong these days, with many companies structuring their HTTP API based on its principles. And yet, I think that REST is a fundamental mistake, that it caused a lot of damage and pain, and that people should just stop creating RESTful HTTP APIs.
  • superfes@lemmy.worldEnglish
    3·
    11 months ago

    So the author has the argument to replace REST … with REST, and somehow we’re just all supposed to be like “genius!”…

  • thisisawayoflife@lemmy.worldEnglish
    3·
    11 months ago

    Yeah I’m not buying it yet. REST is great from my perspective, and the concern about data leakage seems like it could be curtailed significantly by creating an API contract first and clearly defining field in each object and having a proper security audit performed of the data (whoever that is in your organization). By using code generation on the contract, implementing the client and the server are then very straight forward.

  • uhhhhh@lemmy.worldEnglish
    2·
    11 months ago

    I think it’s always good to have discussion around how we can change and improve upon what we’ve done for a long time.

    That said, they completely lost me on “POST on /commands/report-student-lastname-change/version/1”

    Holy crap, now we have to implement one of these for each field that could be changed instead of just using one PATCH? No thank you…