Hey Lewis, thanks for reading! and the article actually agrees with you on that one! This nuances in what should be the use cases for Server Actions are actually the whole point of this article :) Server Actions are POST-only and can't be natively cached, which makes them a poor fit as soon as your data fetching needs any caching or state management. Something like TanStack Query or SWR will serve you much better there. On the API route point, the abstraction still meaningfully reduces boilerplate and makes TypeScript types seamless across boundaries. Similar concept under the hood, very different experience in practice.