|Ask HN: Server daemon, web service or other?|
8 points by polyfractal 857 days ago | 11 comments |
|I'm building an app that requires an adapter/bridge that resides on a server and interfaces with the database. The adapter allows limited database access to third-party servers. I'm trying to determine the best method to implement this adapter.|
I could build a traditional daemon process using C. I'd prefer to avoid this, since working with databases in C isn't my favorite activity. I'm also decidedly mediocre with C and haven't done anything serious with it in ages.
I could build a daemon using a scripting language like Python. I'd feel more comfortable doing this, but I've never daemonized a script before. The code would also have to include network code to be accessible by third-party servers. Is this a good or bad idea? Or nothing unusual?
Lastly, I could build equivalent scripts, but serve them through a web-server. The advantage is that I can defer networking to Apache/nginx/whatever. The downside is that the implementation becomes reliant on an existing web-server, and can't be installed on a system that doesn't have one running.
Thoughts? Am I just over-thinking this?
| Y Combinator