- Taschenbuch: 340 Seiten
- Verlag: CreateSpace Independent Publishing Platform (23. November 2013)
- Sprache: Englisch
- ISBN-10: 1494269279
- ISBN-13: 978-1494269272
- Größe und/oder Gewicht: 21,6 x 2 x 27,9 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 525.904 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Express.js Guide: The Comprehensive Book on Express.js (Englisch) Taschenbuch – 23. November 2013
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Über den Autor und weitere Mitwirkende
Azat Mardanov has over 12 years of experience in web, mobile and software development. With a Bachelor’s Degree in Informatics and a Master of Science in Information Systems Technology degree, Azat possesses deep academic knowledge as well as extensive practical experience. Currently, Azat works as a Senior Software Engineer at DocuSign, where his team rebuilds 50 million user product (DocuSign web app) using the tech stack of Node.js, Express.js, Backbone.js, CoffeeScript, Jade, Stylus and Redis. Recently, he worked as an engineer at the curated social media news aggregator website, Storify.com (acquired by LiveFyre) which is used by BBC, NBC, CNN, The White House and others. Storify runs everything on Node.js unlike other companies. It’s the maintainer of the open-source library jade-browser. Before that, Azat worked as a CTO/co-founder at Gizmo — an enterprise cloud platform for mobile marketing campaigns, and has undertaken the prestigious 500 Startups business accelerator program. Prior to this, Azat was developing he developed mission-critical applications for government agencies in Washington, DC, including the National Institutes of Health, the National Center for Biotechnology Information, and the Federal Deposit Insurance Corporation, as well as Lockheed Martin. Azat is a frequent attendee at Bay Area tech meet-ups and hackathons (AngelHack hackathon ’12 finalist with team FashionMetric.com). In addition, Azat teaches technical classes at General Assembly, Hack Reactor, pariSOMA and Marakana (acquired by Twitter) to much acclaim. In his spare time, he writes about technology on his blog: webAppLog.com which is number one in “express.js tutorial” Google search results. Azat is also the author of Express.js Guide, Rapid Prototyping with JS and Oh My JS; and the creator of open-source Node.js projects, including ExpressWorks, mongoui and HackHall.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
I found this book the best, most comprehensive guide to Express by far.
I am coming from a Rails background, so wrapping your head around middleware and setting up the configuration right, was very new to me as Rails takes care of all those things - for good and worse.
The guide explained middleware finally in a clear and straight forward manor, to the point that I am now almost annoyed with Rails' convention over configuration approach.
The book is built around a heap of great examples, and is structured in a really helpful and methodological breakdown of the main components that make up an Express.js app.
There are here and there some typos, but that is to be expected from a self published book (couldn't imagine myself writing error free), but most importantly they didn't distract me from the great content at all.
What the book is missing, I feel, is a bit more on security (I'd recommend Node.js Security by Dominic Barnes for a quick intro) and a bit more on testing (I'd recommend Node.js in Action for a good breakdown of testing frameworks).
That said, I think this is the simply the single best resource and place to start with Express.
But, the many, MANY typographical errors make it hard to enjoy.
I'm 7 chapters into the book (there are over 30, relatively short and focused).
There certainly is valuable information to be learned here, but it will take effort on your part.
Two major flaws:
#1) The typographical errors wreck the "flow" of the reading by being distracting.
I have to re-read sentences because I think I missed some words, and that keeps me away from focusing on the concepts.
These errors are not misplaced commas or something minor that can be overlooked, these errors wreck the flow.
It's hard to explain, but once you read the Kindle sample, you'll get a feel for what I mean.
#2) It's written from a developer mindset.
You might think this is a good thing, considering this is a "coding" book aimed at developers.
Maybe it is, but having developed a few apps in Express, I've encountered multiple parts of the book where you're told to "use this module!" with little explanation.
The author is correct, I'd also recommend you "use this module!" but I could see people new to Express not quite understanding what we're using or why we're using it.
A specific example that happened twice so far: terminal output.
You're told to execute a command and note the image of the terminal code output.
Instead of explaining what happened in the terminal, it's up to you to interpret the screenshot to see what happened.
Overall, there's just a lot of hopping around and it might take some time to connect the dots.
*** Buy the Kindle Version ***
At the Kindle price, this could be a one-time quick-fix for you to power through without much worry.
The paperback version is ~3x the cost of the Kindle, and is not worth it in my opinion.
I bought this book because it's self published and I like supporting the practitioners that are on the front lines.
Granted, I probably could have seen my criticisms coming, but at the Kindle price, you can't really go wrong.
That's my review and I'm sticking to it :)
Suggestions to the author:
- Please find someone to edit the book so readers can enjoy the lessons you have to share. Happy to work with you on this (I'm in the Bay area)
- (minor) Perhaps focus more on the "why" instead of the "how" - there are many ways to do something, but what's the reasoning behind doing it this one way?
Best practice that's expected by the community? Performance increase? Security strategy? Etc.
- Keeping up with matching new versions of Express and other modules will be tedious, but I'd recommend this book to anyone in a heartbeat if I knew it is always nearly up to date.
What I liked about this book is that it is just about ExpressJS -- not an attempt to show readers how to integrate with other technologies (e.g. the MEAN stack). I needed to review Express independently of other technologies, and the GUIDE seems to do that well.
Part 1 provides a compelling argument for why Express is a good framework for NodeJS. It moves along at a reasonable pace, illustrating to the reader the benefits without waxing poetic.
Part 2 was a bit of a turn-off. Without meaningful explanation for the features listed in this section of the book, the examples really didn't do anything to improve my understanding of this material. The section struck me as filler to fatten the book up. The publisher should have worked with the writer more closely in editing this section to make it more compelling to read. In general, the frequency of forward-looking statements (i.e. "this to be explained later") became distracting to the point of my flipping through pages to skip such content.
Software documentation is readily available online nowadays. The success of a programming book is critically dependent on the author's ability to (a) shed light where online resources cannot, and (b) make the material entertaining enough to keep the reader engaged.
I never made it to Part 3. I am re-attempting this book, so those of you who read this may want to stay tuned for an updated review from me.
After spending several years building web applications and RESTful APIs with ASP.NET MVC, ASP.NET Web API and Ruby on Rails, I choose Node.js for a commercial project in summer 2013. While looking for tutorials on using Express to build web applications with Node.js, I came across Azat's blog and website ([...] & [...] The hands-on, no-nonsense approach in Azat's tutorials helped me decide on Express as the server-side web framework for my project. I bought "Express.js Guide" as a very handy reference while working with Node.js and Express in my project.
"Express.js Guide" details the innards of the Express API, has a number of tips and tricks and finally, four tutorials that helps in "crossing the chasm" between a "Hello, World!" Node.js app and a production-grade web application with Node.js and Express. Azat explains how he built Hackhall ([...] with Node.js, Express, Mongoose, MongoDB & Backbone.js. Hackhall is a great, real-world example that demonstrates how to build a Node.js web application with a RESTful API. The source code is available on Github and Azat happily answers questions on his book and code.
Although there are number of books on Node.js and some of them cover Express to some extent, "Express.js Guide" is the best, easy to read & follow reference that I can recommend to every Node.js developer seriously considering Express for their next Node.js web application.
I don't see any effort put on it and it is really superficial.
The first part is a quick start which well, you can find plenty of blogs about it.
The second part, well, it is not that bad but I feel like it is quite rushed. There are a few topics but it is just a quick run through them.
Tips and tricks is a bunch of 1-2 pages information which are not worthy. Yes, there are a lot of links on them, but I don't buy a book for links.
1 page on auth and then links to passport, good.
It finishes with 4 projects.
Projects are a bunch of screenshots and all the source copied on the book, with almost no explanations.
The big and more worthy project, hackhall is not bad but I don't see the love in it. I am a express noob (that is why I bought the book) but I could do it better, there is a lot of repetitions (checkUser, checkAdmin, db...) and when it was getting excited you see a... Conclusion... ¿Where is the backbone part? Ah, on the source. I can go to github and download plenty of sources for free.
I am sorry, but I wouldn't recommend it.