4 ms·
Brilliant reply, thank you! I think you just persuaded me to switch to AWS. Do you do any work with web sockets? I'm a bit worried about that wrt Python, wheth
by randomsearch 7y ago
Brilliant reply, thank you! I think you just persuaded me to switch to AWS.
Do you do any work with web sockets? I'm a bit worried about that wrt Python, whether it will scale well.
I guess my biggest security concerns are messing up my REST implementation, dependencies in Node being compromised, and vulnerability in servers I'm using, e.g. nginx, redis.
- fpereiro 7y agoI normally don't work with websockets, just JSON, but perhaps that's because all the applications I work on are basically glorified CRUDs. If your application is essentially a CRUD, however, JSON might be more than enough. I've seen thousands of JSON requests/responses per second being handled by small virtual instances running node. The first thing I'll do as soon as the product I'm building starts bringing in revenue will be to pay a security expert to perform a security audit of it all. In the meantime, I try as much as possible to eliminate backdoors (use the API for everything), simplify the data flows, drastically reduce the amount of dependencies and of moving parts, and as much as possible use technology that's been around for a few years (nginx, node and nginx all make the cut :).
- randomsearch 7y agoAs I need to push events/data (collaborative app) I'll need websockets unless I decide to do some insane polling. Totally with you on the security expert, definitely a priority. Thanks a lot for taking the time to reply, you've been really helpful!
- fpereiro 7y agoUsing websockets for a collaborative app makes all the sense in the world (incidentally, I realize I've never written one an app of that kind). My pleasure! Being part of this thread has been an amazing learning experience.