Downloaded 11 times
Uploaded byAdron Hall
Node.js rulz! JavaScript takes over the full Stack
Node.js is a web server written in C/C++ that uses an event-driven and non-blocking I/O model. It allows for fast and easily scalable development using JavaScript and packages from NPM. The document discusses Node.js capabilities and recommends using Express.js, MongoDB, testing frameworks like QUnit and Nodeunit, and deploying applications to a Platform as a Service like Tier 3's Web Fabric for fast prototyping.
More Related Content
Similar to Node.js rulz! JavaScript takes over the full Stack
Node.js rulz! JavaScript takes over the full Stack
- 1. Node.js Rulz! JavaScript takesover the full Stack
- 2. Node.js What is it? What’sit do? Why does it matter? How do we GSD?
- 3. Node.js is... A WebServer A good KISSer Written in C/C++
- 4. Node.js does... Event DrivenI/O Based on V8 Run on *nix & Windows
- 5. Why? Let’s talk aboutthings we hate...
- 6. Why? Let’s talk about things we love...
- 7.
- 8.
- 9. JavaScript It’s the languagewe all know and love (or hate). It’s been around for years!
- 10.
- 11.
- 12. Mongo DB Easy Setup Fast Prototyping
- 13.
- 14. Deployment I’m using Tier3’s Web Fabric PaaS...
- 15. PaaS Built on CloudFoundry .NET Support w/ Iron Foundry More Frameworks than any other
- 16.
Editor's Notes
- #2 Yeah, we keep hearing this. It’s taking over the full stack, at a rapid rate. But what is and how should we dive into Node.js + JavaScript Development against the full stack? What’s available?\n
- #3 What is it, what’s it’s do, why does it matter and how do we get shit done with it?\n
- #4 \n
- #5 Node.js operates differently then most servers in the asynchronous nature that is at the heart of JavaScript, it shoots of events, not waiting for them to be done. Giving single proc machines a distinctive scaling advantage of other systems...\n\nBased on V8, it has a really fast core. A lot of V8 JavaScript executes as fast as managed C#, Java and other modern languages in many circumstances. Sometimes, arguably faster. Scale it based on the evented I/O via stateless systems and you can easily get web scale performance out of it.\n\nIt runs everywhere, with almost complete synchronous feature sets.\n
- #6 As developers, what do we hate?\nBloated frameworks, having excess nonsense to deploy, configuration that bloats, systems that are hard to deploy, systems that require lots and lots of tweaking just to get started with and a whole host of other annoying things.\n\nNode.js is LEAN. It is probably the smallest server you can get in size, with all the frameworks needed to do whatever you’re going to do with it, express.js, jade, bricks.js, or whatever, it’ll still likely be around 1 MB.\n
- #7 Lean frameworks, we’ve got that. We also like things that are fast. CHECK\nWe generally like dynamic languages that have a large community with lots of material about how to do all sorts of things. CHECK\nAn active open source community around the code project, providing a solid base with impeccable support. CHECK\nThe ability to get a basic app up and running in... seconds. CHECK\nThe ability to use existing systems, host on existing environments and new modern and faster environments to host and deploy applications into. CHECK\n\nI could go on, but you get the point. There are a LOT of reasons to love Node.js\n
- #8 To cover the bases... Node is lean, fast, and scalable. Right out of the box. It’s the smallest download you’ll probably have in about a decade for this kind of power. With all that, you can deploy to almost any type of server or environment.\n
- #9 Real quick note, this is a pivital part of Node.js. It’s apparent that the people involved with Node.js have taken a lot of the great things about Ruby on Rails and created them from inception. There are however a lot of things that are annoying that are not there (like a forced active record system or bloated file structure for an application with tons of configuration).\n
- #10 \n
- #11 To start building this, I’m going to dive right in with Node.js and pull in Express.js to get a framework to get something working.\n
- #12 \n
- #13 \n
- #14 \n
- #15 \n
- #16 \n
- #17 \n