Materialized views (that the article talks about) is a related concept, but only a few databases really support that.
Both of these are also related to the work on 'Stream Databases', where the problems of efficient recomputation are central. There is a ton of work on this in academic research (http://www.springer.com/gp/book/9783540286073), but it hasn't been able to gain a foothold in the data management market (several of the academic research projects transitioned into startups).
Postgres triggers are row by row so depending on your use cases they can be quite slow.
Ideally I'd cache all these values and invalidate the global cache through the application. This would require one set of services or each set of services managing their own cache. Anytime a room is updated, boot and reload the cache for that room.
Let the db stay normalized.
No triggers needed.
Not sure what databased that supports it though.