Most the time that would be totally good. Except for time sensative stuff, like polls. They need realtime information for those (you can't wait 20 minutes at talent show, ect, for results). Though perhaps I can have one table with time sensative information, and then leave the rest of the data in the other table.
Wouldn't I still need summary tables? I'd just be updating them less frequently (and not using triggers). Or would I chache it? (the frontend is built on top of codeigniter which has some caching abilities... I think I can just set a cache with an expiry or something to that effect). I think it just stores the summary in a text file and retrieves those results rather than bothering the database...
But a trigger would add minimal overhead and allow for realtime. The user wouldn't see lag at all
(as the user sends a text message, then it gets sent to our modem, and then it gets pushed to our api... even if it added a half second-maybe even a few seconds-no body would notice as the lags between sending and receiving texts between phones are sometimes already 10-15 seconds (or longer depending on carrier,ect) and always at least a full second).
Thoughts? Should I avoid the trigger, and should I use a different method than summary tables?