WebFund 2013W Lecture 14: Difference between revisions
| Line 17: | Line 17: | ||
* [http://caolanmcmahon.com/posts/asynchronous_code_in_node_js/ queue-flow] | * [http://caolanmcmahon.com/posts/asynchronous_code_in_node_js/ queue-flow] | ||
* [http://documentup.com/kriskowal/q/ Q: promises in JavaScript] | * [http://documentup.com/kriskowal/q/ Q: promises in JavaScript] | ||
The author of async also has a nice blog post on [http://caolanmcmahon.com/posts/nodejs_style_and_structure/ node style and structure]. | |||
Revision as of 20:48, 7 March 2013
Databases
- ACID
- Database Transaction
- Transaction Processing
- NoSQL
- Eventual Consistency
- Callbacks
- MongoDB and SQL terminology
- Join
Concurrency in Node
Standard node.js, with its design centered around asynchronous I/O and callbacks, can be annoying if you just want to do more traditional programming tasks such as data processing (read from multiple files and do stuff with it, for example). In general you should be wary of doing too much of this in your main node application as you may kill your performance; however, modern systems are pretty fast so you may be able to do more than you think.
To make it easier to write and understand your code, though, you may want to look at these libraries that implement different approaches to the problem of writing sequential-like code in Node:
The author of async also has a nice blog post on node style and structure.