Wanting to use this with Livewire live form saving

[christoferd]

I'd love to use this with Livewire live form saving.

For example: The app has a calendar booking form that automatically saves edits made in form fields on existing records.
This means the form may save 10 times in 60 seconds. And not necessarily to the same model.

If every change were saved to the database, it would create millions of records in a short amount of time.
Even if I only stored the differences/changes, it would be a lot of records, maybe not so much data.

Issue: I want to keep the main database fast and lean.

Solution?

1. Use a separate database just for Activity? Maybe sqlite3
2. Merge similar records recorded at similar times? By making sure the Activity tracker does not store every single change to a separate record. Idea here is to create a time slot of X seconds. When storing, it will check if there was a previous record within last 300s. (this could be cached) The changed data can be merged. This limits to only one activity record per user per each edited booking per 300s.

Context: The visible calendar has Bookings with its own details, and related to Tasks, Charges, Transactions, Clients, and Vehicles

What would you do?
Have you had to sove this yourself?