Firebase and indexing/search -


i considering using firebase application should people use full-text search on collection of few thousand objects. idea of delivering client-only application (not having worry hosting data), not sure how handle search. data static, indexing not big deal.

i assume need additional service runs queries , returns firebase object handles. can spin such service @ fixed location, have worry availability ad scalability. although don't expect traffic app, can peak @ couple of thousand concurrent users.

architectural thoughts?

long-term, firebase have more advanced querying, it'll support sort of thing directly without having special. until then, have few options:

  1. write server code handle searching. easiest way run server code responsible indexing/searching, mentioned. firebase has node.js client, easy way interface service firebase. of data transfer still happen through firebase, write node.js service watches client "search requests" @ designated location in firebase , "responds" writing result set firebase, client consume.
  2. store index in firebase clients automatically updating it. if want clever, try implementing server-less scheme clients automatically index data write it... index full-text search stored in firebase, , when client writes new item collection, responsible updating index appropriately. , search, client directly consume index build result set. makes lot of sense simple cases want index 1 field of complex object stored in firebase, full-text-search, pretty gnarly. :-)
  3. store index in firebase server code updating it. try hybrid approach index stored in firebase , used directly clients searches, rather have clients update index, you'd have server code updates index whenever new items added collection. way, clients still search data when server down. might stale results until server catches on indexing.

until firebase has more advanced querying, #1 best bet if you're willing run little server code. :-)


Comments

Post a Comment

Popular posts from this blog

Command prompt result in label. Python 2.7 -

i want put result(output) of shell command label. command works, label shows "0", however, in command prompt, result shown correctly, need showed in label. doing ubuntu. myg1 = button(root, text="rodyti informacija", command=lambda: gauti()) myg1.pack(side=bottom) def gauti(): imti = tekstas.get("1.0", "end-1c") info = subprocess.call("id '{imti}' ".format(imti=imti), shell=true) w = label(root, text= info) w.pack(side = bottom) subprocess.call() returns exit code of process created (in case 0 success). if want text output of process, should instead call subprocess.check_output() .
Read more

javascript - How do I use URL parameters to change link href on page? -

i change href value of link using url parameters. example: default <a id="dlink" href="link-1">link</a> but, when user goes https://url.com/?dlink=link-2 it swaps out link new link <a id="dlink" href="link-2">link</a> first need value url. if you're not using javascript framework can create function using jquery. please check get url parameter jquery or how query string values in js it. after that, element "a" id , set value there. $("#dlink").attr("href", hreffromparam);
Read more

amazon web services - AWS Route53 Trying To Get Site To Resolve To www -

so have domain nameservers pointed aws route 53. site hosted on ec2 instance , reachable resolves site.com, if input www.site.com. i'm curious how site resolve www.site.com. have under route53 domains hosted zone 2 additional record sets outside of ns , soa: a site.com ec2 elastic ip cname www.site.com ec2 public dns i can reach site using both site.com , www.site.com, resolve site.com. there way make if enter either, resolves www.site.com? at first, both should record set. a site.com ec2 elastic ip www.site.com ec2 elastic ip and need redirect setting in web server (nginx, apache, ..) following. (source: how redirect www non-www nginx on centos 7 ) redirect non-www www if want redirect users plain, non-www domain www domain, add server block: server { server_name example.com; return 301 $scheme://www.example.com$request_uri; } save , exit. configures nginx redirect requests "example.com" "www.example.com". not
Read more