nosql - Couchbase as read through caching layer in the cloud + backend database -



nosql - Couchbase as read through caching layer in the cloud + backend database -

our web architecture based on commercial products both in memory caching , relational backend database.

in context of investigating moving web stack cloud, looking @ couchbase both caching layer (which sit down in cloud, next apps) potentially replacing internal database couchbase document oriented nosql database (at to the lowest degree read portion).

that mean have create next changes:

asymmetric read/write...the apps read cache write backend systems of record (read >> write). backend systems of record update internal nosql database in turn populate cache implement read through cache....apps in cloud talk in memory caching layer (including xcdr). if objects not found in cache, cache should automatically retrieve info internal backend couchbase db, without application code beingness aware of (not side cache)

so, questions are:

is having cloud based caching layer plus nosql internal backend database valid pattern ? is possible implement read through cache couchbase, i.e. the cb caching layer transparently retrieve info backend db if not found in cache ? if yes, kind of backends supported (relational db's, nosql, couchbase itself) regardless of whether implementing side cache (i.e. apps first talk cache , backend) or read through cache (i.e. apps talk cache, , cache talks backend), how expose couchbase info manipulation api via http, or recommended utilize couchbase sdk across wan links (in terms of latency) ? how memcached api play ?

thx nick

have few questions , comments: q#1, i'd question why need cache when have couchbase already. given can scale out , cache aggresively if want that, caching tier next couchbase buys you? #2, couchbase not have transperant auto population/write-through facility. app need that. #3, sdks give best alternative here. couchbase has compatibility memcached apis using sdks tap total powerfulness of couchbase additional facilities natively available you.

caching nosql cloud couchbase

Comments

Post a Comment

Popular posts from this blog

php - Android app custom user registration and login with cookie using facebook sdk -

php - Android app custom user registration and login with cookie using facebook sdk - i developing android application in users need register , log in using facebook. approximately, flow. open app first time, authenticate facebook, data, send info server create them business relationship in application, start session new business relationship in server, cookie perform later interactions. so far good. what need know wich info have send server, can able identify users when log in seccond time. because need start session in server , send cookie android app farther interactions. i'm using php server side language. i thinking getting getaccesstoken() in android facebook sdk, pass server on business relationship creation , storing in android app. but can't manage how login users on sec time utilize app. any suggestions ? in advance ! to uniquely identify user within app, should create request /me , user's id. guaranteed unique , remain con
Read more

django - Access session in user model .save() -

django - Access session in user model .save() - is possible access current session in user model .save()? pseudo code of want achieve: # users.models.py def save(self, *args, **kwargs): created = true if self.pk: created = false super(abstractuser, self).save(*args, **kwargs) # post-save if created: look_for_invite_in_session_and_register_if_found(self, session) seems wrong in architecture. shouldn't access request in models layer. work request must done in view. can this: user, created = abstractuser.objects.get_or_create(name=name) if created: look_for_invite_in_session_and_register_if_found(user, request.session) django session
Read more

php - .htaccess Multiple Rewrite Rules / Prioritizing -

php - .htaccess Multiple Rewrite Rules / Prioritizing - here current htaccess file: rewriteengine on rewritecond %{http_host} !^www\.website\.com [nc] rewritecond %{http_host} ([^.]+)\.website\.com [nc] rewriterule ^(.*)$ http://www.website.com/gotourl.php?urlid=?%1 [l] rewriterule ^(\w+)$ ./gotourl.php?urlid=$1 [nc,l] rewriterule ^(\w+)/$ ./gotourl.php?urlid=$1 [nc,l] the website in question url shortener i'm working on testing/developing , personal use. above code may not ideal i'm not familiar .htaccess , made via googling , testing. want url shortening aspect: http://website.com/1234 -> http://website.com/gotourl.php?urlid=1234 http://website.com/1234/ -> http://website.com/gotourl.php?urlid=1234 the problem cannot figure out how ignore directories. want specific directories go specific pages: http://website.com/img (or) http://website.com/img/ -> http://website.com/img.php http://website.com/img/1234 (or) http://website.com/
Read more