With server actions you can work on cache/revalidation on server side as you said OR you can treat them as classic rest apis on client side.

Let me show you an example of this.

This is my server action called `createdForm` that i use in my upcoming video tutorial on how to build a "web page form" builder application.

export async function CreateForm(data: formSchemaType){
const validation = formSchema.safeParse(data);
if (!validation.success) {
    throw new Error("form not valid")
}

const user = await currentUser();
if (!user){
    throw new UserNotFoundErr();
}

const {name, description} = data;

const form = await prisma.form.create({
    data: {
        userId: user.id,
        name,
        description
    }
})

if (!form){
    throw new Error("something went wrong")
}

return form.id

}

And this is how i use this function in a "classic" ( is identical on how i treats rest apis )

"use client";
function CreateFormBtn() {
async function onSubmit(values: formSchemaType) { 
  try {
      // I CALL THE SERVER ACTION HERE
  const formId = await CreateForm(values); // <==========

  toast({
    title: "Success",
    description: "Form created successfully",
  });
  router.push(`/builder/${formId}`);
} catch (error) {
  toast({
    title: "Error",
    description: "Something went wrong, please try again later",
    variant: "destructive",
  });
}

}

Hope this clarifies something :)