blocking vs async using guzzle

Thanks. That really cleared up things. Part of what I am doing is to keep a copy of the data logs on S3, and thus not on the mysql database which is running on my same server. That is the reason that I am sending it over to s3. But I am also keeping a local copy of the data in my same database so that users can browse it "realtime". Kind of defeats the purpose? Perhaps the answer is to only keep 2 weeks of current data on my local mysql and if the user wants their data, I can email it to them. I just managed to get the writing of data to the s3 working late last night as a proof of concept. Did I mention that I don't have any users yet? .

Do you know of any automatic way to delete records from a mySQL server when they get aged?

proof that an old dog can learn new tricks