In-Memory Caching and Syncronization with Database Data in Mayocat
20 views
Skip to first unread message
Amal Saha
unread,
Jun 19, 2015, 10:05:22 AM6/19/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to mayoca...@googlegroups.com
Hello,
I see the both DBIABCStore and MemoryABCStore implement the ABCStore interface. For example, TenantStore interface is implemented by MemoryTenantStore.java and DBITenantStore.java classes. The MemoryABCStore.java is documented as in-memory implementation of the interface ABCStore. Here ABC may be Tenant, Product, etc.
Does that mean that automatically Mayocat has implemented an in-memory caching solution? If yes, is there a way to invalidate or synchronise the cache? Will jDBI runtime automatically take care of synchronisation between "memory store" data (data managed by MemoryABCStore) and "database store" data (data from database thru JDBIABCStore)? Here ABC may be Tenant, Product, etc.
Thanks and Regards,
Amal
Jerome Velociter
unread,
Jun 19, 2015, 10:14:51 AM6/19/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Amal Saha, mayoca...@googlegroups.com
Hi Amal,
No, the memory stores aren't initially intended for caching ; but as
(somehow) functional stubs in order to write integration REST tests.
They are not used as of today.