On Sat, Jul 2, 2011 at 8:26 PM, Afkham Azeez <az...@wso2.com> wrote: > > Senaka > Shankar mentioned $subject. Isn't this sub-optimal? For instance, caching > will not reduce the load on the DB in the current implementation. Why has it > been implemented this way? > For the benefit of others who do not know the full context,
Current distributed caching impl is local to a particular node. Whenever the first request for a resource is made, if it's not in the local cache , it gets added. This way there could be several caches of same resource local to different G-Reg instances. When that particular resource is modified through one G-Reg server, a message is being sent to other local caches to invalidate their cached copy. I think was done due to several reasons. - Replicating a large object over distributed cache being an over head - A resource has considerable amount of meta data around it (properties, associations/dependencies, tags, comments, etc). No clear decision on replicating those or not. - Collection & Resource not being serializable Technically, most of these issues can be solved easily. I believe we should at least , - think of distribute caching resources bellow a certain size - Cache certain type of media types (eg. synapse-config, wsdls) which have more tendency to be accessed across cache /sumedha > ---- > Sent from my phone > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
