4 ms·
Update: ------- -- PowerDNS as authoritative server is almost laughably easy. They have a pipe backend and example which would take just a few minutes to rewo
by lzw 16y ago
Update:
-------
-- PowerDNS as authoritative server is almost laughably easy. They have a pipe backend and example which would take just a few minutes to rework in python to pull records from CouchDB. A few minutes more and it could check memcached to see which server is loaded and re-order results appropriately. Geo wouldn't even be that hard to add.
-- Twisted and Tornado might work to replace node.js. It is kinda shocking how many people are investing in node.js, though.
-- If anyone can recommend a caching proxy server that will also work as a sort of template engine and auth engine in front of couchDB, that would be great. I can write this in any number of tools, but if it already exists, great. Remember, it needs to take multiple CouchDB shows/lists and run them thru a template to produce a final resulting html page.
-- CouchDB caches the trees in memory so can quickly tell me if the etag is different, but for commonly used data, I do want to cache it to save time on disk seeks given how dramatic the latency of disks are vs. memory. But only for the most commonly used things.
-- as I originally mentioned, I don't want to reinvent the wheel, I'd rather rent wheels by the hour. Unfortunately, none of the app hosting options offer the kind of wheels I need. The app we're building will involve some heavy lifting, in the 10s of gigabytes of data a day range, with a fair bit of custom processing, and even app engine doesn't provide the kind of indexing we really need (But that CouchDB does well, and incrementally.)
-- I think this might work as an open source project, an open stack for people to use and build upon.
- jchrisa 16y agoI have only used Node.js a little bit so far, but I've been pleased. I'd say at this point it is great for JavaScript business logic. I'd hold off on using it for long running processes like caches or proxies (http server behind a load balancer would be fine, as those are cheap to restart.) Basically Node is solid but has the occasional hiccough. Also the libraries are rapidly evolving. Real life example: CouchOne hosting originally prototyped our proxy in Node.js before @_jhs moved it to Erlang. We still do business logic (async operations) in Node and it's great for that. In a few months it should be ready for prime time in the critical path as well.
- deleted 16y ago[deleted]