Batching database writes in .Net web api to reduce insert frequency

Question

I have some web api's built in various .Net versions which capture data to log into a database, typically using entity framework. I'm considering adding code to batch up multiple database inserts to reduce the frequency of updates. This will make the api calls non-transactional (since the data is not committed yet when the api call is finished) but for this application, this is not a requirement.

My concern is that I'm reinventing something some standard libraries may be doing, but my research usually points to using a message queue of some kind, which doesn't feel like an exact match.

I've even considered an option for just quickly logging the data to log files and then have a background process read through these logs and perform the database updates from there, but a. this feels clunky and b. even if I go that route, I'd prefer to use something already built and not reinvent it.