A materialized view (MV) stores the result of a query on disk, so reads are fast, but the data may be stale between refreshes. (whether it’s eventually consistent or transactionally consistent depends on the database engine)
What you get:
What you trade off:
So I suggest you to use an MV when you prefer read speed and cost predictability over up-to-the-second data.