Use materialized views instead of foreign table for sms data
Meta
Tasks
-
Create a flyway migration that renames the foreign tables to something different - Suggestion:
FT_<Tablename>orForeign_Table_<Tablename>(🤔 I like the second one more)
- Suggestion:
-
Create a flyway migration to create the materialized views based on the renamed foreign tables -
The materialized views also need to have an index on the primary key
-
-
Create a cron job to regularly update the materialized views
Questions/Stuff to think about
- What is a good interval for the cron job?
- As it is not much data, I think we can try 15 minutes
- How do I add the cronjobs to stage/prod
- How must the flyway files be named?
- How to I make sure that the new migrations are executed for a new deployment?
- Is there anything else to keep in mind with the migrations?
Edited by Tobias Kuhnert