10. All operating system functionality can be
accessed asynchronously
Node is built for concurrency
Node requires you to think event-driven and
non-linear
Sunday, April 1, 12
15. One language to rule them all (in theory)
Learning node is all about becoming very
skilled at JavaScript and event-driven
programming
Sunday, April 1, 12
18. Scaling Rails
Have a monsterous DB setup
Cache the shit out of everything
Making the servers more lightweight
Sunday, April 1, 12
19. Reducing Server-side
Complexity
Smaller requests
Ajax and JSON (very cachable!)
More requests, we want real-time
UI logic on the client
Sunday, April 1, 12
24. Sever-side becomes a true “App” Interface
(aka API)
UI flow belongs to the client
Data over Documents
Sunday, April 1, 12
25. More JSON
Routing on the Client
Templates move to the Client too
Static pages matter less
Sunday, April 1, 12
26. Separation between API/platform and UI/client
becomes more vivid.
Developing apps in a team becomes easier.
Automated testing becomes a lot more
managable, less client-server integration tests.
Increased mashupability
Node is perfect for this new “data hub” role of
the server-side
Sunday, April 1, 12