サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
WWDC25
mcollina.github.io
The problem with closures function process (bigdata, cb) { remoteCall(bigdata, function (err, something) { storeSomething(something, function (err, res) { // this function is short-lived and hard to optimize // bigdata is still in scope! cb(null, res * 2) }) }) } Avoid nested closures 1/2 function process (bigdata, cb) { remoteCall(bigdata, function (err, something) { // bigdata exits scope here c
Takeaways Most of the time not used under Roy's guidelines A much nicer version of RPC? No live feed (Server-Sent Events?) Is WebSocket REST? instead of pretending everything is a local function even over the network (which turned out to be a bad idea), what if we did it the other way around? Pretend your components are communicating over a network even when they aren't. Solomon Hykes - @solomonst
Call your consultant! This is not a database ;) History Pills 1960s: From tapes and batch to disks, shared access and interactivity Late 1960s: Navigational Databases, links Early 1970s: Relational Model Late 1970s: SQL Early 1980s: Desktop Databases Late 1980s: Object Oriented Database 2000s: speed and scale, NoSQL Early 2010s: never let a beautiful abstraction go to waste, NewSQL The tiranny of
publish/subscribe protocol multiple quality of service level.. ..with at-least-once and exactly-once semantics low overhead (2 bytes at minimum) offline messaging retained messages, like a key/value store Small core, vibrant community Extreme modularity Reimplement everything in Javascript Why Node.js matters? high performance (2x at Paypal) faster application development (2x at PayPal) batteries
このページを最初にブックマークしてみませんか？
『https://mcollina.github.io/』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
