Curious.. What if you were to store/update/delete the metadata in a database table and query the table to get the results you are wanting? Your add/update (even a delete if this is allowed) would be updating the table, instead of the metadata. This would also remove the need for a job that would cache the results.
It's ultimately what I also went with. I still store metadata on S3 but I do that via an observer on the S3 model. Can interact with the model as normal and then it eventually pushes those changes to S3.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Curious.. What if you were to store/update/delete the metadata in a database table and query the table to get the results you are wanting? Your add/update (even a delete if this is allowed) would be updating the table, instead of the metadata. This would also remove the need for a job that would cache the results.
Thoughts ?
Yes it's a great idea, thank you.
It's ultimately what I also went with. I still store metadata on S3 but I do that via an observer on the S3 model. Can interact with the model as normal and then it eventually pushes those changes to S3.