4 ms·
This sounds like a good fit to me. I'd watch the complexity, though, and see what you can get done with the simplest thing that could possibly work, then build
by jchrisa 16y ago
This sounds like a good fit to me. I'd watch the complexity, though, and see what you can get done with the simplest thing that could possibly work, then build up, always with the end-goal in mind.
- lzw 16y agoThanks for the advice. It is my hope that I can keep the custom code to a bare minimum. There may already be a node based dns server out there, found a couple references, and am hoping the web platform is very minimal, letting me extend it later without changing the appliance itself. As i dig into it more, I may have some contributions to CouchApp to make, but may just end up making the node part of it a separate open source project. Not sure if ill need to hack couchapp or not. Edit: reread your comment. Will start just with couch, then add couch apps, then add simple node server front end, look at node based frameworks, then add executing js in node from the couch, then redis for caching, then add the load balancing, logging and see what features I need for apps.
- jchrisa 16y agoIf you come up with a generic way to run show and list functions in front of Couch in node, that will be useful to many people.