Here is my requirement:
- I would need to use Sql db to perform Create, Update and Delete operations
- I would need to use NoSql to perform Read operations
a)I understand that Create, Update and Delete transactions offer better performance in Sql DB.
b)I understand that Read transactions offer better performance in NoSql DB.
What are the disadvantages of me using Table_PER_CLASS and JOINED, InheritanceType, rather than SINGLE_TABLE for modelling my data persistence layer?
This is a solution I envision: Every time a Create, Update, Delete transaction is performed a mechanism would update the NoSql data accordingly.
Am I going in the right direction with my thought process. Are there better ways of doing this?
Aucun commentaire:
Enregistrer un commentaire