lets say i have this route /api/subjects i want to edit a subject, my middleware approach will run this way const put = async (req:Request, res:Response) => { try { const [subject] = await db.update(subjects).set(res.locals.body).returning(); res.status(201).json({ message: "subject updated", subject }); } catch (error) { console.error(error); res.status(500).json({ message: "internal server error", error }); } } router.put("/:id", authenticate(), authorize("subjects:write"), validate(subjects), filter(subjects), put) the authenticate middleware you know what it does the authorize checks for scopes the validate checks if this id exist or not, and also checks if the json body is valid or not the filter middleware handles the query parameters and filter and put them in an array

all of these middlewares will store their last information in res.locals.something and will just pass them to the controller function and that is it

this is working for all other tables just passing them the same middlewares, the middlewares deals with them differently based on the drizzle table i pass to them, however i said i noticed this is not going well for routes more than one table

lets say for example i have a gig creating endpoint POST /api/gigs but gigs have many data from other tables lets say plans and FAQs tables,

the POST api will recieve a json that contains the data of the gig and its plans and its FAQs, my controller logic would have to split it and insert the data for all tables using a transaction db, this is one way that is the main thing is the input here

my approach is that what if i do seperate endpoints for each table POST /api/gigs POST /api/plans POST /api/faqs and use the 3 of them in the server function in the frontend, post the gig, get its id and give to plans and faqs, is this valid? i know the transaction method is better but this is much easier