WebFund 2013W Lecture 14: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
== | ==Databases== | ||
* [http://en.wikipedia.org/wiki/ACID ACID] | * [http://en.wikipedia.org/wiki/ACID ACID] | ||
* [http://en.wikipedia.org/wiki/Database_transaction Database Transaction] | * [http://en.wikipedia.org/wiki/Database_transaction Database Transaction] | ||
| Line 7: | Line 7: | ||
* [http://en.wikipedia.org/wiki/Callback_%28computer_programming%29 Callbacks] | * [http://en.wikipedia.org/wiki/Callback_%28computer_programming%29 Callbacks] | ||
* [http://docs.mongodb.org/manual/reference/sql-comparison/ MongoDB and SQL terminology] | * [http://docs.mongodb.org/manual/reference/sql-comparison/ MongoDB and SQL terminology] | ||
==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: | |||
* [https://github.com/caolan/async async] ([http://caolanmcmahon.com/posts/asynchronous_code_in_node_js/ blog intro]) | |||
* [http://caolanmcmahon.com/posts/asynchronous_code_in_node_js/ queue-flow] | |||
* [http://documentup.com/kriskowal/q/ q: promises in JavaScript] | |||
Revision as of 19:58, 7 March 2013
Databases
- ACID
- Database Transaction
- Transaction Processing
- NoSQL
- Eventual Consistency
- Callbacks
- MongoDB and SQL terminology
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: